Skip to content

Mzizi tools overview

The Mzizi tooling — @nyuchi/mzizi-mcp, @nyuchi/mzizi-cli (the fundi agent SDK + CLI, in the monorepo’s mzizi-sdk/ directory), and @nyuchi/mzizi-skills — is governed by the Bundu Foundation and operated by Nyuchi as part of the open Mzizi project, and consumed by every Nyuchi codebase. This section documents how Nyuchi uses them; the upstream reference lives in bundu-docs.

Two live MCP surfaces read the same Mzizi document store:

  • https://mzizi.dev/mcp — the portal’s canonical document-route MCP (components, collections, database status).
  • https://mcp.mzizi.dev/mcp — the standalone mzizi-mcp Cloudflare Worker; registry-driven (~60 tools from mcp_tool_registry) behind a free Connect OAuth signup gate.
{
"mcpServers": {
"mzizi": { "type": "url", "url": "https://mzizi.dev/mcp" }
}
}
  • The MCP server we run locally and in CI, the tools it exposes, and how to configure Claude Code / other MCP clients to talk to it.
  • Token handling, registry lookups, and the offline cache.
  • Common workflows: scaffolding a new mini-app, validating component back-links, running the registry health check.
  • Install + minimum-viable usage from a Nyuchi project.
  • The auth helpers (Nyuchi JWT verification, org-scoped clients).
  • The data helpers (typed resource clients, pagination, error envelopes).
  • The UI helpers (Mzizi-aware fetch hooks, error-boundary glue).
  • Versioning policy — when we pin, when we float.
  • The skill library shape, where Nyuchi-specific skills live, how they’re registered.
  • The contribution flow: from a one-off prompt to a versioned skill.
  • Testing skills locally before publishing.