Lost in chat history
The diagram your agent generated is three days deep in a conversation no teammate will ever scroll to.
for AI-assisted development
Diagrams your team reads today. Your agent reads tomorrow.
Your architecture shouldn't live in a chat thread. When Claude, ChatGPT, or Cursor draws the system, DiagramZu gives that diagram a permanent home — versioned, rendered, and shareable with your team.
Works with the agents you already use
- Claude
- Claude Code
- Cursor
- ChatGPT
- MCP
the problem
Diagrams die in screenshots.
Stale the moment it ships
A PNG pasted into a doc can't be re-rendered when the code moves on.
Impossible to hand off
New teammates can't see how the system fits together without re-deriving it from scratch.
how it works
From prompt to shared diagram in three steps.
- 01
Your agent proposes; DiagramZu draws it.
Claude's plan mode (or any MCP client) writes the Mermaid and saves it here. Every diagram lands with a description the next agent can read.
- 02
You review in view-first mode.
Open the diagram, pan and zoom, switch the layout (Dagre or ELK), tweak the code side-by-side when you need to. Every save is a snapshot.
- 03
Hand it to the team.
One public link, pan-and-zoomable, no login. Version history travels with it as institutional memory.
agent-native
Built for the Model Context Protocol.
DiagramZu is an MCP server with 14 tools — create, read, update, and list diagrams, browse folders, walk version history, build decks, leave comments, and analyze a diagram for issues. Claude Code, Cursor, and custom agents read and write your diagrams directly — no copy-paste.
One-click in Claude Claude users can add diagramzu as a custom connector and authorize with their account — no API token to copy. The token setup still wires up Cursor, ChatGPT, and every other MCP client.
Add to Claude Code
claude mcp add --scope user --transport http diagramzu https://mcp.diagramzu.ai/mcp \
--header "Authorization: Bearer dz_live_xxx"- 2:14 PMAdd streaming workerby Claude
- 1:48 PMSplit read/write pathsby Claude
- 1:31 PMInitial system mapby you
- 12:55 PMBootstrapby Claude
version history
Every change, captured.
Every save is a versioned snapshot. Open the history drawer to see how the architecture moved, what your AI changed last Tuesday, and why. The diagram becomes the running record — readable now by humans, readable later by the next agent.
embed anywhere
Your diagrams, live in someone else's docs.
Paste one iframe and the diagram renders in place — pan-and-zoom, theme-matched, always current — inside your docs, Notion, blog, or wiki. Each embed links quietly home, and you can see how many times it loaded in the last 7 days.
what you get
Everything your diagrams need.
Folders
Nest and organize diagrams per space.
Public sharing
View-only links with pan & zoom, no account required.
Multi-language
English, 繁體中文, 简体中文, and 日本語 out of the box.
Real-time render
See the diagram update as the code changes.
Layout engines
Switch between Dagre and ELK per diagram — pick the layout that reads best for the shape of your system.
AI diagram analysis
Your agent can call analyze_diagram to read the rendered shape, not just the Mermaid source — feedback on the picture, not the prose.
Embeddable
Drop a live, pan-zoom diagram into your docs, Notion, or blog with one iframe — it re-renders when the source moves on.
Decks
Group diagrams into an ordered deck and present them full-screen — the same source your engineers reviewed, ready for the room.
Comments
Pin comments to any node to review an AI-proposed diagram together, then clear them as the design settles.
what it's for
Three workflows DiagramZu was built for.
Review AI proposals
Reading a diagram is faster than reading 600 lines of AI-proposed prose. Turn on review and an agent's edit waits as a proposal — diff it, then approve or reject before it overwrites.
Hand architecture to the team
One shareable link. Version history records how the system evolved. New engineers see the living map, not a stale wiki.
Reuse in presentations
The same diagram a CTO reviews lives on in CEO and CPO decks. One source of truth across engineering and exec surfaces.
why diagramzu
Why not just…?
…paste a screenshot in a doc?
A PNG can't re-render when the code moves, and no one can edit it. DiagramZu keeps the source — re-themed, re-laid-out, and current every time you open it.
…use a local render tool?
Local Mermaid tools draw the diagram and forget it. Nothing persists, nothing's shareable. DiagramZu is the home that outlives the session — one link, full history, no login to view.
…type prompts into another diagram app?
Your agent already drew the diagram while doing the real work. DiagramZu catches it through MCP — you don't retype the prompt into a second tool that bolts AI onto a canvas.