Mzizi Mcp

io.github.nyuchiPublished by GitHub account nyuchiv0.9.1Updated Sep 30, 2026

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

The publisher's own server: Concierge

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Read-only MCP server over the Mzizi design system registry, letting an assistant look up nodes, components and ownership data.

What you can do
Query the Mzizi design system registry for design nodes and their details. Look up registered components and the documents that describe them. Check ownership information attached to registry entries. Access is read-only, backed by row-level security on the component documents table.
When to use it
Useful when an assistant needs to reference a team's Mzizi design system while working on UI or component questions, and only read access to the registry is needed.
Requirements
Runs as a remote endpoint or as a local npm package over stdio. Needs the SUPABASE_PUBLISHABLE_KEY environment variable; SUPABASE_URL is optional and defaults to the canonical project. Network access to the Supabase project is required.
Before you install
The server asks for a Supabase publishable (anon) key, which grants read-only access to the component documents table; treat it as a credential and do not share it beyond the intended project. Registry queries go to a third-party Supabase project.

Installation

In SourceWeft

  1. Open Mzizi Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.nyuchi%2Fmzizi-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mzizi": {
      "type": "http",
      "url": "https://mcp.mzizi.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.9.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Iconic-Expeditions integrations