Skip to content
Agentmart
Submit a tool

DiagramZu

Let Claude, Cursor, or ChatGPT author Mermaid diagrams your team can read and share.

Connector by diagramzu.aiOfficial · Domain verified by the MCP Registry

IndexedMITRemote (HTTP)★ 1
Write a review

Install

Works with Claude Code, VS Code, Cursor, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install connector/diagramzu-ai-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Remote endpoint

  • https://mcp.diagramzu.ai/mcp Remote (HTTP)

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Let Claude, Cursor, or ChatGPT author Mermaid diagrams your team can read and share.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
12 read · 7 write · 0 delete
Secrets
None asked for
Install scripts
Nothing to install (hosted)
Runs as
Hosted (remote endpoint)

Tools by what they do 19

Read from the source code; the running server may list different tools.

Read 12 · Look things up without changing anything.

  • analyze_diagram
  • get_deck
  • get_diagram
  • get_page
  • get_version
  • list_comments
  • list_decks
  • list_diagrams
  • list_folders
  • list_pages
  • list_spaces
  • list_versions

Write 7 · Create, change, send or run things.

  • add_comment
  • create_deck
  • create_diagram
  • create_page
  • update_deck
  • update_diagram
  • update_page

Network hosts it talks to 1

  • mcp.diagramzu.ai · found in remote endpoint, install command

Tools (19)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • add_comment

    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.

  • analyze_diagram

    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.

  • create_deck

    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 Spac…

  • create_diagram

    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.

  • create_page

    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 wo…

  • get_deck

    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).

  • get_diagram

    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.

  • get_page

    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.

  • get_version

    Fetch one snapshot by id. Returns its title, mermaid source code, and metadata. Read-only — restore is human-only in the UI.

  • list_comments

    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.

  • list_decks

    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.

  • list_diagrams

    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.

  • list_folders

    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.

  • list_pages

    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.

  • list_spaces

    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.

Show 4 more tools
  • list_versions

    List manual snapshots of a diagram, newest first. Returns id, label, title, createdAt, and createdBy for each.

  • update_deck

    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.

  • update_diagram

    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.

  • update_page

    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.…

Signals

Stars
1
Forks
0
Open issues
1
Last commit
Oct 12, 2026 (16 days ago)
Last release
Jun 16, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
ai.diagramzu/mcp
Version
0.0.3
Auth
Auth not stated
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 25, 2026
Cite this page

DiagramZu MCP server. Agent Mart. https://agentmart.dev/connectors/diagramzu-ai-mcp (last updated 2026-10-25)