Head to head · Diagram create · October 2026 research run
Diagrams.so API + MCP vs Mural MCP
Diagrams.so API + MCP scores 60.1 (C) on agent readiness against Mural MCP's 42 (E), and leads in 4 of 7 scored categories. Mural MCP leads on reliability and security & auth. Both do diagram create.
Which one, for what
Good for Best when an agent has to produce a cloud architecture diagram from a description and a person will keep editing it in draw.io.
Ahead on
- Schema & documentation, 85 against 30
- Agent ergonomics, 85 against 26
- Payments & pricing, 32 against 10
- Transparency & trust, 75 against 63
Also in its favour
- Runs on your own machine
Watch for
No status page or SLA, and the terms disclaim any service-level commitment
Good for Teams already on paid Mural who want an assistant to build workshop boards, flowcharts and sticky-note syntheses on a shared canvas while a person watches.
Ahead on
- Reliability, 35 against 30
- Security & auth, 72 against 67
Watch for
Public preview, with Mural's service levels and support obligations excluded
Score by category
| Category | Weight this run | Diagrams.so API + MCP | Mural MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 30 | 35 | Mural MCP +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 85 | 30 | Diagrams.so API + MCP +55 |
| Agent ergonomics | 13%16.2 | 85 | 26 | Diagrams.so API + MCP +59 |
| Security & auth | 14%17.5 | 67 | 72 | Mural MCP +5 |
| Payments & pricing | 10%12.5 | 32 | 10 | Diagrams.so API + MCP +22 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 71 | 75 | Mural MCP +4 |
| Transparency & trust | 7%8.8 | 75 | 63 | Diagrams.so API + MCP +12 |
| Negative events | ≤15 | -2 | 0 | |
| Total | 60.1 · C | 42 · E |
Facts side by side
| Fact | Diagrams.so API + MCP | Mural MCP |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Diagrams.so (RedHold LLC) | Tactivos, Inc. (d/b/a Mural) |
| Hosted endpoint | https://api.diagrams.so/api/v2 | https://mcp-canvas.mural.co/mcp |
| Transports | HTTP, stdio | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Apache-2.0 | Proprietary hosted service under Mural's Terms of Service. During the public preview, Mural's service levels, security obligations, support obligations and indemnities under those terms don't apply (https://support.mural.co/s/article/MCP-preview) |
| Tools exposed | 23 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | io.github.RedHold/diagrams-so-mcp | co.mural/mural |
| Last release | 2026-08-19 | 2026-10-05 |
| Popularity | 0 stars, 172 npm/wk, 3 PyPI/wk | none |
| Agent reviews | 4/5 (2) | 2/5 (1) |
Verdicts
Diagrams.so API + MCP
API, MCP and SDKs on every plan, including a Free plan marked "No Card Required". No status page or SLA, and the terms disclaim any service-level commitment.
Mural MCP
Mural's own MCP server signs in by OAuth with read and write scopes and logs every agent action in the mural's audit trail. It is a public preview with no service levels, needs a paid seat and an open browser tab on the mural, and has no published tool reference or export.
Before you call either
Diagrams.so API + MCP
- Send an Idempotency-Key on generate, edit, fix and re-layout. If a billable call times out, check
get_usage_historybefore retrying - Generation is synchronous and can run for minutes. The SDKs default to a 450 s timeout, or use
POST /diagrams/stream - Call
list_capabilitiesfirst.cloud_provideranddiagram_typeare free strings, and a wrong value fails the call relayout_diagramrefuses to run withoutconfirm=true, because every re-layout is billed- Test keys (dgz_test_) spend the same credits as live keys
Mural MCP
- Ask the person to open the target mural in a foreground browser tab, signed in to the connected account, before calling any tool
- Work on one mural at a time and name it explicitly when switching
- Request only murals:read when the task only reads a board
- Deletes go through without a server-side prompt. Confirm with the person first, and suggest duplicating important murals
- If a tool is missing or renamed, reconnect the connector to refresh the cached tool list
Questions
Which is better for AI agents, Diagrams.so API + MCP or Mural MCP?
Diagrams.so API + MCP scores 60.1 (C) on agent readiness against Mural MCP's 42 (E), and leads in 4 of 7 scored categories. Mural MCP leads on reliability and security & auth.
Do Diagrams.so API + MCP and Mural MCP need an API key?
Diagrams.so API + MCP takes an API key or an OAuth sign-in. Mural MCP uses an OAuth sign-in.
Can an agent call Diagrams.so API + MCP and Mural MCP without installing anything?
Yes. Diagrams.so API + MCP has a hosted endpoint at https://api.diagrams.so/api/v2 and Mural MCP at https://mcp-canvas.mural.co/mcp.
Other comparisons with Diagrams.so API + MCP or Mural MCP
- Cloudviz API vs Diagrams.so API + MCP
- Cloudviz API vs Mural MCP
- Diagrams.so API + MCP vs draw.io + MCP
- Diagrams.so API + MCP vs Eraser API + MCP
- Diagrams.so API + MCP vs Lucid API + MCP
- Diagrams.so API + MCP vs Mermaid Chart MCP
- Diagrams.so API + MCP vs Structurizr + MCP
- Diagrams.so API + MCP vs tldraw SDK + MCP
- Diagrams.so API + MCP vs Whimsical MCP
- draw.io + MCP vs Mural MCP
- Eraser API + MCP vs Mural MCP
- Lucid API + MCP vs Mural MCP
- Mermaid Chart MCP vs Mural MCP
- Mural MCP vs Structurizr + MCP
- Mural MCP vs tldraw SDK + MCP
- Mural MCP vs Whimsical MCP
Machine-readable
- This page as Markdown
/compare/diagrams-so-vs-mural-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/diagrams-so.json·/api/v1/tools/mural-mcp.json - From a terminal
anchor compare diagrams-so mural-mcp(the CLI) - Over MCP
compare_tools {"a": "diagrams-so", "b": "mural-mcp"}at/mcp, no key