# mzizi-mcp MCP server

Read-only MCP over the Mzizi design system registry — nodes, components, ownership.

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-nyuchi-mzizi-mcp
- Repository: https://github.com/nyuchi/mzizi-tools
- Website: https://mzizi.dev

## Install
- Command: `npx -y mzizi-mcp`
- Endpoint: https://mcp.mzizi.dev/
- Auth: Auth required by registry metadata

## Setup notes
- Package: Npm mzizi-mcp v0.1.0
- Environment variable: SUPABASE_URL (default https://grjsboqkaywpwatvrzmy.supabase.co)
- Environment variable: SUPABASE_PUBLISHABLE_KEY (required)
- The upstream registry signals required auth or secrets.
- Remote endpoint: https://mcp.mzizi.dev/

## Tools
- list_components - List components from the document store. Optionally filter by node (1–10) or owner (bundu | nyuchi | mzizi | framework). Returns the lean index — use get_component for the full document. Endpoint: https://mcp.mzizi.dev/
- get_component - Fetch one component as its full JSON document — one read, everything in it (metadata, owner, sources/descriptors, legacy source code, files, docs). Endpoint: https://mcp.mzizi.dev/
- list_collections - List the per-node collections (n1_tokens … n10_documentation) with total counts and ownership breakdown. Endpoint: https://mcp.mzizi.dev/
- get_database_status - Diagnostic info — Supabase connection health and document-store row count. Endpoint: https://mcp.mzizi.dev/

## Resources
- mzizi://components - Mzizi component registry index — one row per component (name / node / collection / owner). The full document is available via the get_component tool.
- mzizi://nodes - Per-node collection summary — counts and ownership breakdown.

## Prompts
Not captured

## Metadata
- Owner: io.github.nyuchi
- Version: 0.1.0
- Runtime: Npm
- Transports: STDIO, HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: May 24, 2026
- Source: https://registry.modelcontextprotocol.io