io.github.mzizi-dev/mzizi-mcp · v0.13.0 · docs-and-knowledge
io.github.mzizi-dev/mzizi-mcp is healthy: it completed an MCP handshake in 1819 ms and exposes 14 tools.
Mzizi design system MCP: components, tokens, skills and docs. Free; sign-in only for Fundi.
Endpoint: https://mcp.mzizi.dev/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 14 |
| Latency | 1819 ms |
| Last checked (UTC) | 2026-10-16T10:50:39.913Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T10:50:39.913Z | Healthy | 1819 | |
| 2026-10-15T06:05:44.626Z | Healthy | 3171 |
mzizi_search | Search the registry by words: components, conventions, AI instruction sets and releases. Start here when you do not know the exact name of what you want. A component hit with `rustCrate` has a Mzizi Roots (Rust) implementation, which is the lead; at an equal score it ranks first. Documentation pages |
mzizi_get_component | Fetch one component in full, Rust first. When the component has a Mzizi Roots (Rust, Dioxus) implementation, `rust` comes first: its crate, the `cargo add` line, its CONTRACT clause block and the `.rs` source inline. `astro` follows when the component has a pure Astro implementation (mzizi-registry# |
mzizi_list_components | The registry index, optionally filtered by node, owner, collection, type or rust. Returns a lean row per component (name, type, node, owner, collection, and rustCrate when it has a Mzizi Roots (Rust) implementation, which is the lead) — use get_component for one component in full, or search when you |
mzizi_get_tokens | The Mzizi brand system: 21 colour families (7 minerals, 7 heritage, 7 experimental), semantic colours, typography, spacing, radii and the ecosystem brands. Ask for `colors` to get every colour family in one call. |
mzizi_get_architecture | The Mzizi DNA double helix — nodes, rungs and strands — with live counts. Pass `node` for one node's covenant, stakeholder and implementation rules. |
mzizi_get_doctrine | How to build here: Ubuntu pillars and principles, mzizi conventions, and the AI instruction sets. |
mzizi_get_skills | List the published Mzizi agent skills, or fetch one in full. Skills are what an agent loads first. Each skill has a category: `dev` (how every agent works in every repo: digital-hygiene and progress-report — load these before any dev work), `design`, `language` or `build`. Pass `category` to get eve |
mzizi_check_accessibility | Contrast and colour-vision checks against the Mzizi APCA/AAA floor. Computed locally — no network, no upstream dependency. |
mzizi_report_issue | Report a problem with a component or the registry. It goes to your own issue desk — a Durable Object holding your reports — which reproduces it via fundi, drafts an issue body including what the reproduction actually returned, and logs it to fundi. fundi files the GitHub issue with its proposed fix |
mzizi_fundi | Delegate a task to the fundi agent, or check on one. Submit-and-poll: `submit` returns a task id immediately and never waits for the run. Needs sign-in: fundi runs as your Mzizi console user. |
mzizi_mcp_describe | What this MCP server exposes: its tools, which are free and which need sign-in, what each replaces, and where its data comes from. |
docs_search_mzizi | [docs.mzizi.dev] Search across the Mzizi knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Mzizi, find specific documentation, understand how features work, or locate implementation details. The search return |
docs_query_docs_filesystem_mzizi | [docs.mzizi.dev] Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Mzizi documentation pages. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox ba |
docs_submit_feedback | [docs.mzizi.dev] Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback |