DiagramZu
DiagramZu's MCP server lets AI clients read, create, update, and analyze Mermaid diagrams — plus comments, version history, and presentation decks — inside your DiagramZu workspaces.
Workspaces:
list_spacesshows every workspace the token can act in, your role, and the default; other tools take an optionalspace(id, slug, or exact name).Browse:
list_diagrams(search withq, sort by created/updated/title/relevance, filter by folder or owner) andlist_folders(nested paths, up to two levels).Read/write diagrams:
get_diagramby id;create_diagramandupdate_diagramfor title, description, Mermaid code (≤50 KB), folder, and visual style presets (midnight,paper,forest,ocean,mono).Layout control:
styleOptionsfor line, arrow, curve, spacing, and layout engines (dagre,elk.*, orauto).Structure analysis:
analyze_diagramreports orphan nodes, hubs, cycles, and clusters for flowcharts, and can post findings as node-pinned comments.Version history:
list_versionsandget_version(read-only; restoring is human-only);update_diagramcan snapshot a pre-edit version with a label.Comments:
list_comments(filter by node, include/exclude resolved) andadd_comment(pin to a node or reply one level deep) for human-visible review feedback.Decks:
list_decks,get_deck,create_deck, andupdate_deckassemble existing diagrams into an ordered slideshow (declarative slide lists).Link behavior: tools return members-only
/app/...URLs; public share links are deliberately never minted by the server and must be created by a person via the Share button.
Connect over hosted HTTP (https://mcp.diagramzu.ai/mcp with a dz_live_… Bearer token) or local stdio via npx -y @diagramzu/mcp.
Provides tools to create, update, and analyze Mermaid diagrams stored on diagramzu.ai.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
@diagramzu/mcp
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.
Related MCP server: AI Diagram Maker MCP Server
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/mcpwith environment:
DIAGRAMZU_BASE_URL=https://diagramzu.ai
DIAGRAMZU_API_TOKEN=dz_live_xxx
DIAGRAMZU_SPACE_ID=<your space id> # optionalDIAGRAMZU_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_spacesshows 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
Tool | Description |
| List every workspace this connection can act in, with ids, slugs, roles, and which is the default |
| List diagrams in the Space (filter with |
| List folders in the Space |
| Fetch one diagram by id (title, description, Mermaid source) |
| Create a new diagram (returns its id and its |
| Update title, Mermaid source, description, or style of an existing diagram |
| Get a structural summary of a diagram (nodes, edges, density) |
| List version history for a diagram |
| Fetch a specific historical version of a diagram |
| List a diagram's comments, oldest first (optionally only one node's thread) |
| Post a comment, optionally pinned to a node or replying to a thread |
| List presentation decks in the Space, newest-edited first |
| Fetch one deck by id, with its ordered slides |
| Assemble existing diagrams into an ordered presentation deck |
| Change a deck's title, description, or slide order ( |
| List the workspace's Markdown pages (id, title, revision, snippet; filter with |
| Fetch one page by id — the whole body, or just its outline or one section |
| Create a Markdown page (title comes from the body's front matter or first heading) |
| Edit a page: targeted |
Which URLs are public
Two different things get called "a link" here, and only one of them works for someone outside your Space:
URL | Who can open it |
| Space members only — the diagram in the app. |
| Space members only — the deck's presentation view. |
| Space members only — the Markdown page in the app. |
| Anyone with the link — the public, read-only diagram page. |
| Anyone with the link — the public, read-only deck. |
| Anyone with the link — the public, read-only Markdown page. |
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:
[](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-diagramzu
pnpm install
pnpm run build
# point your client at: node dist/index.js
# with DIAGRAMZU_BASE_URL / DIAGRAMZU_API_TOKEN (DIAGRAMZU_SPACE_ID optional)License
MIT
Available Tools
19 toolsadd_commentAInspect
Post a comment on a diagram. Pass nodeId to pin it to a specific node, or parentId to reply to an existing top-level comment (threads are one level deep). The author is the API token's owner. Use this to leave structured review findings a human will see on the diagram.
Inputs: body (required), diagramId (required), space, nodeId, +1 more.
analyze_diagramAInspect
Analyze a stored flowchart diagram's structure (nodes, edges, subgraphs) and return actionable findings — orphan nodes, over-connected hubs, cycles, disconnected clusters, and grouping suggestions. Flowchart diagrams only. Set postAsComments: true to also persist each finding as a comment on the diagram (node-pinned where the finding names a single node) so a human reviewer sees them on the diagram surface.
Inputs: id (required), space, postAsComments.
create_deckAInspect
Create a presentation deck from existing diagrams. Pass slides as the complete ordered list of diagram ids — the deck plays them as a slideshow in that order. Typical flow: create_diagram for each slide, collect the returned ids, then create_deck with those ids in presentation order. Returns the deck id and the present URL, which only members of this Space can open — it is NOT a shareable link. To share the deck outside the Space, someone in the Space opens it in DiagramZu and uses its Share button, which mints a public read-only presentation link. Diagram ids must already exist in this Space (use list_diagrams to find them).
Inputs: space, title, slides, description.
create_diagramAInspect
Create a new diagram in the Space. Returns its id and its URL in the app, which only members of this Space can open — it is NOT a shareable link. To show the diagram to anyone outside the Space, someone in the Space opens it in DiagramZu and uses its Share button, which mints a public read-only link. See this server's instructions for diagram-type selection and class role names (edge/core/data/accent/muted) for color-grouping.
Inputs: code, space, style, title, +3 more.
create_pageAInspect
Create a Markdown page in the workspace — a design write-up, a decision record, a runbook, the prose a diagram cannot carry. The title comes from the body (front-matter title, else the first top-level # heading), so begin the body with a heading rather than passing title. Embed a stored diagram by putting its id inside a fenced diagramzu block; an inline mermaid block is for a throwaway sketch nobody will revisit. Returns the page's id, its revision and its URL in the app, which only members of this workspace can open. To let somebody outside the workspace read it, a person in the workspace opens the page in DiagramZu and uses its Share button, which mints a public read-only link.
Inputs: body (required), lang, space, title, +1 more.
get_deckAInspect
Fetch one deck by id. Returns its title, description, and the ordered list of slides (each slide is a diagram id + title in presentation order).
Inputs: id (required), space.
get_diagramAInspect
Fetch one diagram by id. Returns its title, description (the agent's brief), mermaid source code, and its URL in the app — which only members of this Space can open. If the diagram already has a public link, that link is reported separately on a Share (public, read-only): line; a public link is minted by a person, from the diagram's Share button. Read the description before editing — it tells you what the diagram is for and when to update it.
Inputs: id (required), space.
get_pageAInspect
Fetch one Markdown page by id. Returns its body, its revision — pass that as baseRevision when replacing the whole body — its language, who edited it last, and its URL in the app, which only members of this workspace can open. To let somebody outside the workspace read it, a person in the workspace opens the page in DiagramZu and uses its Share button, which mints a public read-only link. For a long document prefer outline: true (the heading tree, with an anchor per heading) and then section: '<heading text or anchor>' for just the part you need.
Inputs: id (required), space, outline, section.
get_versionAInspect
Fetch one snapshot by id. Returns its title, mermaid source code, and metadata. Read-only — restore is human-only in the UI.
Inputs: diagramId (required), versionId (required), space.
list_commentsAInspect
List comments on a diagram, oldest first. Returns id, parentId (null for a top-level comment), nodeId (the pinned node, if any), author, resolved state, and a body snippet. Use nodeId to fetch only the thread pinned to one node.
Inputs: diagramId (required), limit, space, nodeId, +2 more.
list_decksAInspect
List presentation decks in the configured Space, newest-edited first. A deck is an ordered set of existing diagrams shown as a slideshow. Returns each deck's id, title, and slide count.
Inputs: space.
list_diagramsAInspect
List diagrams in the configured Space (every folder, newest first by default). Use this BEFORE create_diagram to check whether a diagram with the target purpose already exists — if it does, prefer update_diagram over creating a duplicate. Filter with q (case-insensitive substring on title, description, or code) when looking for a named diagram (e.g. q: 'schema' or q: 'infra'). Sort with sort: 'updated' to find the most recently changed diagrams, or sort: 'relevance' when q is set so a title hit ranks above a description or code hit.
Inputs: q, sort, owner, space, +1 more.
list_foldersAInspect
List every folder in the configured Space, ordered by name. Returns id and full path (e.g. 'Infra/AWS' for a nested folder). Use this BEFORE create_diagram or update_diagram when you want to place a diagram in a meaningful folder — agents should match by name (e.g. find a folder named 'Schemas' and pass its id as folderId). Folders are at most two levels deep. Creating folders is currently human-only.
Inputs: space.
list_pagesAInspect
List the workspace's Markdown pages, most recently edited first. Returns each page's id, title, revision, last-edit time, who edited it, and a short snippet — never the full body; call get_page for that. Filter with q, a case-insensitive substring over title and body that works in Chinese and Japanese too, and pass sort: 'relevance' with it so a title hit ranks first. Call this BEFORE create_page to see whether a page on the topic already exists — prefer update_page over writing a second one.
Inputs: q, sort, owner, space, +1 more.
list_spacesAInspect
List every workspace this connection can act in. Returns each workspace's id, slug, name, your role, and which one is the default (the workspace used when a tool is called without space). Call this FIRST when the user mentions a workspace by name, or when you are not sure which workspace the work belongs in — then pass the id as space on the tool you actually want. A connection scoped to a single workspace returns just that one.
Inputs: no named parameters.
list_versionsAInspect
List manual snapshots of a diagram, newest first. Returns id, label, title, createdAt, and createdBy for each.
Inputs: diagramId (required), limit, space, offset.
update_deckAInspect
Update a deck's title, description, and/or slide order. slides is DECLARATIVE: pass the complete desired ordered list of diagram ids — reorder, add, and remove are all expressed by sending the new full list (any id omitted is removed from the deck; new ids are appended in the order given). Returns the deck id and the present URL, which only members of this Space can open — it is NOT a shareable link. To share the deck outside the Space, someone in the Space opens it in DiagramZu and uses its Share button, which mints a public read-only link.
Inputs: id (required), space, title, slides, +1 more.
update_diagramAInspect
Update an existing diagram's title, description, mermaid source, visual style preset, and/or layout style options. When rewriting the source, keep or restore class assignments using the role names from this server's instructions so the diagram stays color-grouped. In a workspace with proposal review enabled, your change is recorded as a proposal pending human approval rather than applied to the live diagram — in that case tell the user you've proposed the change and share the review URL.
Inputs: id (required), code, space, style, +6 more.
update_pageAInspect
Update a Markdown page. EXACTLY ONE body mode, and edits is the one to reach for: each edit replaces an oldText that must appear exactly once in the page, so a change to one paragraph never sends — or silently reverts — the rest of the document. If somebody else edits the page first, YOUR edits are re-applied on top of THEIR text, and the call is refused outright if they changed the very span you are editing. The other mode is baseRevision plus body, which replaces the whole document and needs the revision get_page reported. Changing only metadata (title, folderId, lang) needs neither. Returns the page's new revision and its URL in the app, which only members of this workspace can open. To let somebody outside the workspace read it, a person in the workspace opens the page in DiagramZu and uses its Share button, which mints a public read-only link.
Inputs: id (required), body, lang, edits, +6 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 19 tools
Each of the 19 tools targets a distinct resource (space, folder, page, diagram, version, comment, deck) plus action, and descriptions clearly demarcate boundaries such as list_pages vs get_page vs update_page, or list_versions vs get_version. There is no apparent overlap.
Consistent verb_noun pattern throughout (list_folders, create_page, update_diagram, get_deck, add_comment, analyze_diagram), with only the single-word analyze_diagram as a reasonable verb.
19 tools is on the high side but fairly scoped across eight resources: spaces, folders, pages, diagrams, versions, comments, and decks. It is neither thin nor extreme.
Broad coverage across the core domain (CRUD for pages, diagrams, decks; reads for versions, comments), though folders are read-only and deleting diagrams/decks/comments is absent. These gaps are workable since some operations are intentionally human-only.
Maintenance
Related MCP Connectors
Render, verify, describe, and safely edit Mermaid diagrams through MCP.
Create and manage Mermaid.js flowcharts and diagrams with AI agents via MCP.
Publishes what an AI made — a page, a markdown or PDF doc, or a whole site — to a live HTTPS link. Runs locally over stdio from the @drop2run/mcp npm package, or hosted at https://mcp.dropto.run/mcp for chats that connect by URL.
One memory, every AI. A shared, user-owned markdown memory your AI clients read and write over MCP.
Related MCP Servers
- AlicenseBqualityDmaintenance❤️ Generate mermaid diagram and chart with AI MCP dynamically.11,025 npm652TypeScriptMIT
- AlicenseAqualityDmaintenanceMCP server for AI Diagram Maker — generate software engineering diagrams from natural language, code, ASCII diagram, images, or Mermaid. Inline diagram rendering using MCP apps UI and diagram URL in responses. Works with Cursor, Claude Desktop, Claude Code, and any MCP-compatible AI.5134 npm10MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI to create, edit, and manage Mermaid diagrams via MCP, with real-time preview in a browser-based editor.3-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with a local Mermaid diagram editor via MCP, allowing them to get and set diagrams programmatically.13Apache 2.0