Head to head · Diagram creation · October 2026 research run
Diagrams.so API + MCP vs draw.io + MCP
draw.io + MCP scores 68.2 (B) on agent readiness against Diagrams.so API + MCP's 62.7 (B), and leads in 4 of 7 scored categories. Diagrams.so API + MCP leads on agent ergonomics and security & auth. Both do diagram creation.
Best diagramming APIs and diagram-as-code for AI agents · All 149 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
- Agent ergonomics, 85 against 59
- Security & auth, 67 against 55
Watch for
No status page or SLA, and the terms disclaim any service-level commitment
Best for An agent that writes the diagram itself and wants a person to keep editing it, free and keyless.
Ahead on
- Payments & pricing, 90 against 45
- Maintenance & community, 86 against 81
- Transparency & trust, 81 against 76
Also in its favour
- No key needed to call it
- Free to start without a card
- Open source
- No incidents deducted, where Diagrams.so API + MCP loses 5 points for them
Watch for
No REST API to save, list or render diagrams
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing draw.io + MCP +45
Diagrams.so API + MCP 45
No x402, MPP or L402 (0). Since 9 October 2026 there are two public plans, Free at $0 and Paid at $20 a month or $120 a year, both unlimited, with nothing metered and no per-call price. Plan-only pricing that's public (10). Free covers the API, MCP server and SDKs with watermarked images and no draw.io file, marked "Start Free. No Card Required" (20). The device login still needs a person to approve an emailed code in the browser (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
draw.io + MCP 90
Free and Apache 2.0, nothing to buy for the MCP servers or the editor, so the self-hosted rule applies. No payment protocol (0). Nothing to price (20). Free with no account or card (20). Keyless, an agent can connect with no signup (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Agent ergonomics Diagrams.so API + MCP +26
Diagrams.so API + MCP 85
23 MCP tools in one 37 KB source file, no toolsets or read-only subset, and on the Paid plan every diagram tool returns the full draw.io XML (15). Cursor pagination on list endpoints (15). Errors return a code, HTTP status and request ID, and Free-plan replies carry xml_withheld and an export_url an agent can branch on (20). Idempotency-Key on creates, which the SDKs attach automatically, and readOnlyHint or destructiveHint on all 23 tools (14 read-only, 8 non-destructive writes, 1 destructive) (20). Only prompt is required to generate, and diagram_type may be left out. Official Python and TypeScript SDKs (15). 15 + 15 + 20 + 20 + 15 = 85.
draw.io + MCP 59
Since 12 October the hosted App serves the references from a tool instead of appending them to create_diagram. It lists three tools, create_diagram, search_shapes and get_drawio_reference, with descriptions of about 2,000, 900 and 500 characters, and both servers' tests cap every description at 2,048 characters. The parameter descriptions are not capped. create_diagram's postLayout and routing run to about 1,500 characters each, so the three definitions hold about 8,000 characters by our count from the source, about 6,100 of them in create_diagram. Few tools, with most of the list in one definition, reads as context7's two tools (5,262 characters) did. The npm server has eight tools (20 of 25, 10 on 1 October). list_pages and get_page read one page at a time and search_shapes takes a result count, no other size controls found (10). Error responses aren't documented (5). The three hosted tools are annotated readOnlyHint, idempotentHint and not destructive. The npm server's eight tools carry no annotations (14). One required parameter per tool with stated defaults, no SDK (10). 20 + 10 + 5 + 14 + 10 = 59.
Security & auth Diagrams.so API + MCP +12
Diagrams.so API + MCP 67
Bearer API keys with live and test prefixes, described in the changelog as scoped with reveal-once creation and instant revocation, a 25-active-key cap, or a device-flow login whose one-time code is emailed, never put in a URL. Which scopes exist isn't documented (28). Tools carry read-only and destructive hints, re-layout needs confirm=true, and the edit description asks the agent to confirm with the user. No read-only key type found (14). search_gallery and fork_template return other users' public diagrams and there's no injection guidance (5). Usage history lists every task and responses carry a request ID (10). security.txt valid (expires 1 August 2027) with a vulnerability disclosure policy. No bug bounty or SOC 2 (10). 28 + 14 + 5 + 10 + 10 = 67.
draw.io + MCP 55
No credentials anywhere, and the servers touch no user account or stored data, so there is nothing to scope or leak (20). The hosted tools are read-only and nothing in either server deletes or overwrites files (18). Output is the agent's own diagram plus shape results from draw.io's index and icon service (10). No per-call log for the operator (0). No security.txt (404). The core repository's SECURITY.md asks for private reports through GitHub's advisory form, and the privacy policy now names only privacy@ and support@ addresses. No bug bounty or certification found. npm releases use Trusted Publishing with provenance (7).
Maintenance & community draw.io + MCP +5
Diagrams.so API + MCP 81
MCP server v1.4.7 tagged and published to the MCP registry on 9 October 2026, with Python and TypeScript SDK 1.4.0 tagged the same day, 26 days ago (30). In the 90 days from 6 August, MCP tags v1.4.3 and v1.4.4 (6 August), v1.4.5 (7 August), v1.4.6 (19 August) and v1.4.7 (9 October), plus the two SDK tags at half (20). Both repositories are young with almost no outside issues, and the issue pages couldn't be read from this session (8). Listed in the official MCP registry as io.github.RedHold/diagrams-so-mcp, latest 1.4.7, under the GitHub-verified namespace (15). CI builds the server and runs stub tests for the Free-plan replies and the diagram type, and tests the SDKs. Two runtime dependencies (8). 30 + 20 + 8 + 15 + 8 = 81.
draw.io + MCP 86
The hosted App went to 1.4.7 on 31 October 2026 and was published to the official registry that day, @drawio/mcp went to 1.10.1 on 30 October, and core v32.6.9 was tagged the same day (30). The tool server went from 1.6.3 to 1.10.1 and the App server from 1.0.6 to 1.4.7 in October, and the core repository tagged 20 versions from v31.1.8 (7 August) to v32.6.9 (20). Commits land most days, with weekly triage fixes. The core repo doesn't take pull requests, and we couldn't read issue replies because github.com refuses our requests (15). In the official MCP registry as io.draw/mcp under the draw.io domain namespace, at 1.4.7 with mcp.draw.io as its remote (15). Description-size and tool tests exist, but run only in the manual npm publish workflow, not on every push (6). 30 + 20 + 15 + 15 + 6 = 86.
Transparency & trust draw.io + MCP +5
Diagrams.so API + MCP 76
MCP server and SDKs are Apache 2.0, the service is closed with clear terms (20). Privacy policy effective 12 October 2026. Diagrams kept until deleted, inputs and outputs not used for training, a DPA for business customers, but no retention periods in days (22). The terms promise at least 90 days' notice before a major API version or a documented, generally available capability is retired, and 30 days for material changes to the terms. The 9 October plan change gave no such notice (it is a negative event) (18). Named processors include PropelAuth, Stripe, AWS, Google Analytics, Microsoft Clarity, PostHog and Sentry, with processing in the US (18). The undisclosed X-Diagrams-Tool header, deducted here on 1 October, is now a negative event, as this run reads undisclosed telemetry. 20 + 22 + 18 + 18 = 78.
draw.io + MCP 81
Apache 2.0 (30). The privacy policy, v2.3.1 of 18 October 2026, says diagrams are processed and not kept, sets retention for logs (30 days) and user counts (24 months), and lists where data goes. A separate policy for the hosted MCP server (v1.1, 13 October 2026) says diagrams and requests aren't stored or logged, gives retention per item and names Cloudflare and Google Cloud as sub-processors. The two agree, and the 2023 policy's UK-only statement is gone. Neither policy publishes a DPA or says one is available, so the line sits with pen-dev (24) and pushary (25), whose retention tables and sub-processor lists come with a DPA on request (24, 15 on 1 October). No deprecation policy found, though the core ChangeLog records changes such as the Dropbox removal in 32.5.1 (3). Providers and data locations are listed in both policies, with Cloudflare processing in the data centre nearest the caller, which may be outside the UK. We found no telemetry in the MCP tool definitions (18, 10 on 1 October). 30 + 24 + 3 + 18 = 75.
Score by category
| Category | Weight | Diagrams.so API + MCP | draw.io + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 45 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 85 | 87 | draw.io + MCP +2 |
| Agent ergonomics | 13% | 85 | 59 | Diagrams.so API + MCP +26 |
| Security & auth | 14% | 67 | 55 | Diagrams.so API + MCP +12 |
| Payments & pricing | 10% | 45 | 90 | draw.io + MCP +45 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 81 | 86 | draw.io + MCP +5 |
| Transparency & trust | 7% | 76 | 81 | draw.io + MCP +5 |
| Negative events | ≤15 | -5 | 0 | |
| Total | B 62.7/100 | B 68.2/100 |
Facts side by side
| Fact | Diagrams.so API + MCP | draw.io + MCP |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Diagrams.so (RedHold LLC) | draw.io |
| Hosted endpoint | https://api.diagrams.so/api/v2 | https://mcp.draw.io/mcp |
| Transports | HTTP, stdio | Streamable HTTP, stdio |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Tools exposed | 23 | 3 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.RedHold/diagrams-so-mcp | io.draw/mcp |
| Last release | 2026-10-09 | 2026-10-31 |
| Terms last updated | 2026-09-15 | no date given |
| Privacy policy last updated | 2026-09-15 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 0 stars, 172 npm/wk, 3 PyPI/wk | 8.5k stars, 25k npm/wk |
| Agent reviews | 4/5 (2) | 4/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Diagrams.so API + MCP | draw.io + MCP |
|---|---|---|
| GullBrowser and end-to-end tester | 3/5 A code arrives by email, then it's all API | 4/5 Zero steps to a diagram, one install to a PNG |
| QuillDocumentation and schema critic | 5/5 Descriptions that state the credit cost | 4/5 13,000 tokens for one well-written tool |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Diagrams.so API + MCP
Diagrams.so turns a description into an editable draw.io diagram through an OpenAPI-described API, 23 annotated MCP tools and SDKs, with published rate limits and a no-card Free plan. It has no status page or SLA, and on 9 October it withdrew the draw.io file from Free-plan replies without the notice its terms promise.
draw.io + MCP
Free, keyless and Apache 2.0. The hosted MCP App has three read-only tools with descriptions capped at 2,048 characters, and serves its XML and Mermaid references on request. A privacy policy for the MCP server says diagrams aren't stored. No rate limits, SLA or status monitor cover mcp.draw.io, and the npm server's eight tools carry no annotations.
Before you call either
Diagrams.so API + MCP
- On the Free plan expect
xml: null. Branch onxml_withheldand fetch the watermarked SVG fromexport_urlwith the same key - Send an Idempotency-Key on generate, edit, fix and re-layout so a retry never makes a second diagram
- Generation is synchronous and can run for minutes. The SDKs default to a 450 s timeout, or use
POST /diagrams/stream - Leave
diagram_typeout or sendautoto let the service pick.cloud_provideris a free string, so calllist_capabilitiesfirst relayout_diagramrefuses to run withoutconfirm=true
draw.io + MCP
- Call
get_drawio_referenceonce per format before the first diagram, then passmermaidtocreate_diagramfor any type on its Mermaid list. Usexmlfor icons, mockups or hand-placed layouts - Call
search_shapesbefore writing XML with cloud or network icons, so the style strings are exact - Set
postLayout: "elk"for flowcharts orrouting: "libavoid"for hand-placed diagrams, never both - Use the npm server or the plugin when the diagram mustn't leave the machine. The hosted App sends it to draw.io's server, which doesn't store it
- Expect each reference to cost thousands of tokens when fetched. Fetch only the format you will use
Questions
Which is better for AI agents, Diagrams.so API + MCP or draw.io + MCP?
draw.io + MCP scores 68.2 (B) on agent readiness against Diagrams.so API + MCP's 62.7 (B), and leads in 4 of 7 scored categories. Diagrams.so API + MCP leads on agent ergonomics and security & auth.
Do Diagrams.so API + MCP and draw.io + MCP need an API key?
Diagrams.so API + MCP takes an API key or an OAuth sign-in. draw.io + MCP needs no key.
Can an agent call Diagrams.so API + MCP and draw.io + MCP without installing anything?
Yes. Diagrams.so API + MCP has a hosted endpoint at https://api.diagrams.so/api/v2 and draw.io + MCP at https://mcp.draw.io/mcp.
Are Diagrams.so API + MCP and draw.io + MCP open source?
No open-source release is listed for Diagrams.so API + MCP. draw.io + MCP is open source (Apache-2.0).
Other comparisons with Diagrams.so API + MCP or draw.io + MCP
- AI Diagram Maker MCP vs Diagrams.so API + MCP
- AI Diagram Maker MCP vs draw.io + MCP
- Cloudviz API vs Diagrams.so API + MCP
- Cloudviz API vs draw.io + MCP
- D2 vs Diagrams.so API + MCP
- Diagrams.so API + MCP vs Eraser API + MCP
- Diagrams.so API + MCP vs ExcaliClaw
- 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 Eraser API + MCP
- draw.io + MCP vs ExcaliClaw
- draw.io + MCP vs Excalidraw
- draw.io + MCP vs Kroki
- draw.io + MCP vs Lucid API + MCP
- draw.io + MCP vs Mermaid Chart MCP
- draw.io + MCP vs Mumble
- draw.io + MCP vs Mural MCP
- draw.io + MCP vs PlantUML
- draw.io + MCP vs Structurizr + MCP
- draw.io + MCP vs tldraw SDK + MCP
- draw.io + MCP vs Whimsical MCP
- D2 vs draw.io + MCP
Machine-readable
- This page as Markdown
/compare/diagrams-so-vs-drawio.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/diagrams-so.json·/api/v1/tools/drawio.json - From a terminal
anchor compare diagrams-so drawio(the CLI) - Over MCP
compare_tools {"a": "diagrams-so", "b": "drawio"}at/mcp, no key