All servers · Code & repositories · Build & deploy · Images & design
io.github.mzizi-dev/mzizi-mcp
io.github.mzizi-dev/mzizi-mcp · v0.13.0
Has write/delete toolsTools changed (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Has destructive tools (destructiveHint) |
| Capabilities declared | resources, tools |
| Tool definitions | 14 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Mzizi design system MCP: components, tokens, skills and docs. Free; sign-in only for Fundi.
Connect
streamable-http · https://mcp.mzizi.dev/mcp
claude mcp add --transport http mzizi-mcp https://mcp.mzizi.dev/mcp{
"mcpServers": {
"mzizi-mcp": {
"url": "https://mcp.mzizi.dev/mcp"
}
}
}Tools as reported by the server
mzizi_searchSearch 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 pagesmzizi_get_componentFetch 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_componentsThe 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 youmzizi_get_tokensThe 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. For text, use each family's `textLight` / `textDark` on the base surface, and `onContaimzizi_get_architectureThe Mzizi DNA double helix — nodes, rungs and strands — with live counts. Pass `node` for one node's covenant, stakeholder and implementation rules.mzizi_get_doctrineHow to build here: Ubuntu pillars and principles, mzizi conventions, and the AI instruction sets.mzizi_get_skillsList 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 evemzizi_check_accessibilityContrast and colour-vision checks against the Mzizi APCA/AAA floor. Computed locally — no network, no upstream dependency.mzizi_report_issueReport 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 fixmzizi_fundiwrite/deleteDelegate 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_describeWhat 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 returndocs_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 badocs_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
Tool changes
- 2026-10-22: mzizi_search, mzizi_get_component, mzizi_list_components, mzizi_get_tokens, mzizi_get_architecture, mzizi_get_doctrine, mzizi_get_skills, mzizi_check_accessibility, mzizi_report_issue, mzizi_fundi, mzizi_mcp_describe, docs_search_mzizi
- 2026-10-21: mzizi_search, mzizi_get_component, mzizi_list_components, mzizi_get_tokens, mzizi_get_architecture, mzizi_get_doctrine, mzizi_get_skills, mzizi_check_accessibility, mzizi_report_issue, mzizi_fundi, mzizi_mcp_describe, docs_search_mzizi
- 2026-10-16: mzizi_search, mzizi_get_component, mzizi_list_components, mzizi_get_tokens, mzizi_get_architecture, mzizi_get_doctrine, mzizi_get_skills, mzizi_check_accessibility, mzizi_report_issue, mzizi_fundi, mzizi_mcp_describe, docs_search_mzizi
Repository · Website · JSON · Text for agents · Registry updated 2026-10-06