{
  "markdown": "# @diagramzu/mcp\n\n[![smithery badge](https://smithery.ai/badge/jack08300/diagramzu-mcp)](https://smithery.ai/server/jack08300/diagramzu-mcp)\n\nMCP server for [diagramzu.ai](https://diagramzu.ai). Lets Claude Code, Claude Desktop, Cursor, Windsurf, ChatGPT custom GPTs, and any [MCP](https://modelcontextprotocol.io) client read and write Mermaid diagrams in your Space.\n\nYou author diagrams by talking to your AI — it stores them at `diagramzu.ai/d/<id>`, where your team can read and share them.\n\n> Available in the official [MCP Registry](https://registry.modelcontextprotocol.io) as `ai.diagramzu/mcp`.\n\n## 1. Get a token\n\nSign up at [diagramzu.ai](https://diagramzu.ai), then create an API token at [diagramzu.ai/app/settings/connections](https://diagramzu.ai/app/settings/connections). Tokens look like `dz_live_…` and are scoped to one Space — no separate space-id needed.\n\n## 2. Connect your client\n\nThe hosted server is the easy path: no install, no build. Just paste a config.\n\n### Claude Code\n\n```bash\nclaude mcp add --scope user --transport http diagramzu https://mcp.diagramzu.ai/mcp \\\n  --header \"Authorization: Bearer dz_live_xxx\"\n```\n\n### Claude Desktop, Cursor, Windsurf, Cline\n\nAdd 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.):\n\n```json\n{\n  \"mcpServers\": {\n    \"diagramzu\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp.diagramzu.ai/mcp\",\n      \"headers\": { \"Authorization\": \"Bearer dz_live_xxx\" }\n    }\n  }\n}\n```\n\n### ChatGPT custom GPT (Actions)\n\nIn 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.\n\n### Local stdio (for clients that don't speak remote MCP)\n\n```bash\nnpx -y @diagramzu/mcp\n```\n\nwith environment:\n\n```\nDIAGRAMZU_BASE_URL=https://diagramzu.ai\nDIAGRAMZU_API_TOKEN=dz_live_xxx\nDIAGRAMZU_SPACE_ID=<your space id>\n```\n\nMost users should prefer the remote HTTP transport above — the stdio path exists for clients without HTTP MCP support.\n\n## Tools\n\n| Tool | Description |\n|---|---|\n| `list_diagrams` | List diagrams in the Space (filter with `q`, sort by `updated` / `created`) |\n| `list_folders` | List folders in the Space |\n| `get_diagram` | Fetch one diagram by id (returns title + Mermaid source) |\n| `create_diagram` | Create a new diagram (returns the share URL) |\n| `update_diagram` | Update title and/or Mermaid source of an existing diagram |\n| `analyze_diagram` | Get a structural summary of a diagram (nodes, edges, density) |\n| `list_versions` | List version history for a diagram |\n| `get_version` | Fetch a specific historical version of a diagram |\n\n## Show off your setup\n\nIf 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:\n\n```markdown\n[![MCP: diagramzu](https://diagramzu.ai/badge/mcp.svg)](https://diagramzu.ai)\n```\n\nRenders as a small shields-style badge — gray `MCP` + indigo `diagramzu`.\n\n## Local development (this repo)\n\nFor hacking on diagramzu itself, build from source:\n\n```bash\ncd packages/mcp-diagramzu\npnpm install\npnpm run build\n# point your client at: node dist/index.js\n# with DIAGRAMZU_BASE_URL / DIAGRAMZU_API_TOKEN / DIAGRAMZU_SPACE_ID\n```\n\n## License\n\nMIT\n",
  "bytes": 3357,
  "sha": "9955aee2697becdd9d5cb3021b26ed832d812dc9c3e391bbcdad9c4eae6fcec2",
  "repo_slug": "yenchieh/diagramzu-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_ai_diagramzu_mcp_e8ccb5cc/readme"
}