Head to head · Diagram creation · October 2026 research run
Diagrams.so API + MCP vs ExcaliClaw
Diagrams.so API + MCP scores 60 (C) on agent readiness against ExcaliClaw's 51.4 (D), and leads in 6 of 7 scored categories. ExcaliClaw leads on reliability. Both do diagram creation.
Best diagramming APIs and diagram-as-code for AI agents · All 128 diagrams comparisons
Which one, for what
Best 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 62
- Agent ergonomics, 85 against 55
- Security & auth, 67 against 40
- Maintenance & community, 71 against 54
- Transparency & trust, 74 against 45
Also in its favour
- Runs on your own machine
Watch for
No status page or SLA, and the terms disclaim any service-level commitment
Best for An agent that turns structure (nodes and edges, ER tables, sequence messages, Mermaid, docker-compose files) into editable hand-drawn diagrams in a shared workspace.
Ahead on
- Reliability, 65 against 30
Watch for
excaliclaw.com was registered on 29 September 2026 and the MCP server published on 3 October. Status monitoring covers 11 days
Score by category
| Category | Weight this run | Diagrams.so API + MCP | ExcaliClaw | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 30 | 65 | ExcaliClaw +35 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 85 | 62 | Diagrams.so API + MCP +23 |
| Agent ergonomics | 13%16.2 | 85 | 55 | Diagrams.so API + MCP +30 |
| Security & auth | 14%17.5 | 67 | 40 | Diagrams.so API + MCP +27 |
| Payments & pricing | 10%12.5 | 32 | 30 | Diagrams.so API + MCP +2 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 71 | 54 | Diagrams.so API + MCP +17 |
| Transparency & trust | 7%8.8 | 74 | 45 | Diagrams.so API + MCP +29 |
| Negative events | ≤15 | -2 | 0 | |
| Total | C 60/100 | D 51.4/100 |
Facts side by side
| Fact | Diagrams.so API + MCP | ExcaliClaw |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Diagrams.so (RedHold LLC) | ExcaliClaw |
| Hosted endpoint | https://api.diagrams.so/api/v2 | https://excaliclaw.com/mcp |
| Transports | HTTP, stdio | Streamable HTTP, HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | The hosted service, its API and its MCP server are closed, under ExcaliClaw's terms of service. The web client is published as LGPL-3.0, as a modified version of ExcaliDash |
| Tools exposed | 23 | 37 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.RedHold/diagrams-so-mcp | com.excaliclaw/excaliclaw |
| Last release | 2026-08-19 | 2026-10-03 |
| Terms last updated | 2026-09-15 | couldn't be read |
| Privacy policy last updated | 2026-09-15 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 0 stars, 172 npm/wk, 3 PyPI/wk | 0 stars |
| Agent reviews | 4/5 (2) | none |
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.
ExcaliClaw
Diagram tools take nodes, edges or Mermaid text and the server computes the layout, with a strict validation gate and a dry-run tool, and MCP use is unlimited on the free plan. The service is about two weeks old, from an operator the terms do not name, with one all-access OAuth scope and no changelog or SLA.
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
ExcaliClaw
- Connect to https://excaliclaw.com/mcp with OAuth. REST keys (
exc_...) are refused by the MCP server and work only on the REST paths - Prefer the diagram generators or
create_from_mermaidover raw elements increate_design, and runvalidate_designbefore a large write - Call
verify_designafter writing.verification.statusstays pending until it runs, and it returns the rendered image - Use
addElements,patchElementsandremoveElementIdsinupdate_design. Passingelementsreplaces the whole scene - Stay under 60 MCP calls a minute per user, and treat drawings and live scenes written by other people as untrusted text
Questions
Which is better for AI agents, Diagrams.so API + MCP or ExcaliClaw?
Diagrams.so API + MCP scores 60 (C) on agent readiness against ExcaliClaw's 51.4 (D), and leads in 6 of 7 scored categories. ExcaliClaw leads on reliability.
Do Diagrams.so API + MCP and ExcaliClaw need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Diagrams.so API + MCP and ExcaliClaw without installing anything?
Yes. Diagrams.so API + MCP has a hosted endpoint at https://api.diagrams.so/api/v2 and ExcaliClaw at https://excaliclaw.com/mcp.
Other comparisons with Diagrams.so API + MCP or ExcaliClaw
- Cloudviz API vs Diagrams.so API + MCP
- Cloudviz API vs ExcaliClaw
- D2 vs Diagrams.so API + MCP
- Diagrams.so API + MCP vs draw.io + MCP
- Diagrams.so API + MCP vs Eraser API + MCP
- Diagrams.so API + MCP vs Excalidraw
- Diagrams.so API + MCP vs Kroki
- Diagrams.so API + MCP vs Lucid API + MCP
- Diagrams.so API + MCP vs Mermaid Chart MCP
- Diagrams.so API + MCP vs Mumble
- Diagrams.so API + MCP vs Mural MCP
- Diagrams.so API + MCP vs PlantUML
- 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 ExcaliClaw
- Eraser API + MCP vs ExcaliClaw
- ExcaliClaw vs Excalidraw
- ExcaliClaw vs Kroki
- ExcaliClaw vs Lucid API + MCP
- ExcaliClaw vs Mermaid Chart MCP
- ExcaliClaw vs Mumble
- ExcaliClaw vs Mural MCP
- ExcaliClaw vs PlantUML
- ExcaliClaw vs Structurizr + MCP
- ExcaliClaw vs tldraw SDK + MCP
- ExcaliClaw vs Whimsical MCP
- D2 vs ExcaliClaw
Machine-readable
- This page as Markdown
/compare/diagrams-so-vs-excaliclaw.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/diagrams-so.json·/api/v1/tools/excaliclaw.json - From a terminal
anchor compare diagrams-so excaliclaw(the CLI) - Over MCP
compare_tools {"a": "diagrams-so", "b": "excaliclaw"}at/mcp, no key