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
Your architecture shouldn't live in a chat thread.
When you ask Claude, ChatGPT, or Cursor to draw the system, DiagramZu gives those diagrams a home — versioned, rendered, and shareable with your team.
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 8 tools — create, read, update, list, browse folders, walk versions, and analyze a diagram for issues. Claude Code, Cursor, and custom agents read and write your diagrams directly — no copy-paste.
Add to Claude Code
claude mcp add --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.
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.
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. The agent drops the diagram here; you approve it here.
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.