Diagramzu MCP server
{
"mcpServers": {
"diagramzu": {
"type": "http",
"url": "https://mcp.diagramzu.ai/mcp"
}
}
}{
"mcpServers": {
"diagramzu": {
"type": "http",
"url": "https://mcp.diagramzu.ai/mcp"
}
}
}{
"mcpServers": {
"diagramzu": {
"type": "http",
"url": "https://mcp.diagramzu.ai/mcp"
}
}
}{
"servers": {
"diagramzu": {
"type": "http",
"url": "https://mcp.diagramzu.ai/mcp"
}
}
}{
"mcpServers": {
"diagramzu": {
"type": "http",
"url": "https://mcp.diagramzu.ai/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.0.3
What it does
An MCP server for diagramzu.ai that lets AI clients create, read, and update Mermaid diagrams stored in a shared Space. Diagrams are accessible at a public URL so teams can view and share them. Intended for developers using MCP-compatible clients such as Claude, Cursor, Windsurf, or ChatGPT.
- Ask an AI assistant to generate a Mermaid flowchart and save it to a shared team Space via create_diagram.
- Retrieve an existing diagram by ID to review or edit its Mermaid source through an AI conversation.
- List and browse all diagrams in a Space, filtered or sorted, to find a specific diagram for updating.
Tools this server exposes
| Tool | Does |
|---|---|
| list_diagrams | List diagrams in the Space, with optional text filter and sort by updated or created date. |
| list_folders | List folders in the Space. |
| get_diagram | Fetch a single diagram by ID, returning its title and Mermaid source. |
| create_diagram | Create a new diagram and return its share URL. |
| update_diagram | Update the title and/or Mermaid source of an existing diagram. |
| analyze_diagram | Return a structural summary of a diagram including nodes, edges, and density. |
| list_versions | List the version history for a diagram. |
| get_version | Fetch a specific historical version of a diagram. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.