DiagramZu

@diagramzu/mcp

[smithery badge]

MCP server for diagramzu.ai. Lets Claude Code, Claude Desktop, Cursor, Windsurf, ChatGPT custom GPTs, and any MCP client read and write Mermaid diagrams in your Space.

You author diagrams by talking to your AI — it stores them in your Space at diagramzu.ai/app/d/<id>, where your team can read them and publish a public link.

Available in the official MCP Registry as ai.diagramzu/mcp.

1. Get a token

Sign up at diagramzu.ai, then create an API token at diagramzu.ai/app/settings/connections. Tokens look like dz_live_… and are scoped to one Space — no separate space-id needed.

2. Connect your client

The hosted server is the easy path: no install, no build. Just paste a config.

Claude Code

claude mcp add --scope user --transport http diagramzu https://mcp.diagramzu.ai/mcp \  --header "Authorization: Bearer dz_live_xxx"

Claude Desktop, Cursor, Windsurf, Cline

Add to your client's MCP config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS for Claude Desktop, ~/.cursor/mcp.json for Cursor, etc.):

{  "mcpServers": {    "diagramzu": {      "type": "http",      "url": "https://mcp.diagramzu.ai/mcp",      "headers": { "Authorization": "Bearer dz_live_xxx" }    }  }}

ChatGPT custom GPT (Actions)

In the GPT builder, add an MCP server action pointing to https://mcp.diagramzu.ai/mcp with a Bearer-token authentication header set to your dz_live_… token.

Local stdio (for clients that don't speak remote MCP)

npx -y @diagramzu/mcp

with environment:

DIAGRAMZU_BASE_URL=https://diagramzu.aiDIAGRAMZU_API_TOKEN=dz_live_xxxDIAGRAMZU_SPACE_ID=<your space id>   # optional

DIAGRAMZU_SPACE_ID is optional. Left unset, the server uses the token's own default workspace — the one chosen when the token was minted. Set it to pin a different workspace as the default for this process.

Most users should prefer the remote HTTP transport above — the stdio path exists for clients without HTTP MCP support.

Workspaces

A token is scoped either to one workspace or to all the workspaces its owner belongs to, chosen when the token is authorized (the consent page's Access radio, or Settings → API tokens). An account-scoped token follows its owner's live memberships: joining a workspace adds it, being removed from one closes it on the next call.

• list_spaces shows every workspace this connection can act in, which one is the default, and your role in each.
• Every other tool takes an optional space — a workspace id, slug, or exact name (case-insensitive). Omit it to act in the default workspace. A name matching more than one workspace is refused rather than guessed; pass the id or slug.
• Every tool result ends with the workspace it acted in.
• Returned /app/... links carry ?space=, so opening one switches the browser to that workspace when you are a member.

Tools

Which URLs are public

Two different things get called "a link" here, and only one of them works for someone outside your Space:

The tools hand back the /app/… URLs, so a link pasted straight out of a chat is a members-only one: send it to someone outside the Space and they land on sign-in. To publish, open the diagram, deck or page in DiagramZu and use its Share button. This MCP server deliberately ships no tool that mints a public link — not because a token cannot (a dz_live_… token can mint one over the REST API), but because publishing a Space's content should be a deliberate human action rather than a side effect of a conversation. Once a diagram has a public link, get_diagram and update_diagram report it on a Share (public, read-only): line of their own.

A Markdown page is shared the same way. diagramzu.ai/s/pg/<slug> is its public, read-only address, minted by a person from the page's Share button, so get_page, create_page and update_page print the members-only /app/pages/<id> URL and point at that button for anything wider. They do NOT look a page's link up: unlike get_diagram they report no Share (public, read-only): line, so a page's public address is something a human hands over, not something an agent discovers.

Show off your setup

If you publish your MCP / Claude Code config in a dotfiles or example repo, drop this in the README so the next person knows where the diagrams come from:

[![MCP: diagramzu](https://diagramzu.ai/badge/mcp.svg)](https://diagramzu.ai)

Renders as a small shields-style badge — gray MCP + indigo diagramzu.

Local development (this repo)

For hacking on diagramzu itself, build from source:

cd packages/mcp-diagramzupnpm installpnpm run build# point your client at: node dist/index.js# with DIAGRAMZU_BASE_URL / DIAGRAMZU_API_TOKEN (DIAGRAMZU_SPACE_ID optional)

License

MIT