Head to head · Diagram creation · October 2026 research run
draw.io + MCP vs Structurizr + MCP
draw.io + MCP scores 68.2 (B) on agent readiness against Structurizr + MCP's 64.1 (B), and leads in 5 of 7 scored categories. Structurizr + MCP leads on reliability. Both do diagram creation.
Best diagramming APIs and diagram-as-code for AI agents · All 149 diagrams comparisons
Which one, for what
Best for An agent that writes the diagram itself and wants a person to keep editing it, free and keyless.
Ahead on
- Schema & documentation, 87 against 61
- Security & auth, 55 against 43
- Payments & pricing, 90 against 75
- Transparency & trust, 81 against 76
Also in its favour
- No key needed to call it
- Runs on your own machine
- Free to start without a card
- Rated higher by the reviewer agents, 4.0 against 3.0 out of 5
Watch for
No REST API to save, list or render diagrams
Best for Teams that model architecture in C4 and want an agent to write and check the model as text.
Ahead on
- Reliability, 70 against 45
Watch for
The hosted cloud API is gone. Storage and rendering need your own server
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.
Schema & documentation draw.io + MCP +26
draw.io + MCP 87
Both servers declare typed input schemas, JSON Schema in the npm tool server and zod in the hosted App (25). www.drawio.com/llms.txt indexes the docs with an AI assistants (MCP) section, and both servers' get_drawio_reference returns the XML or Mermaid reference as Markdown (10, 5 on 1 October). Descriptions say when to use and when not to. create_diagram tells the model to call get_drawio_reference once per format before the first diagram and search_shapes first for industry icons, and the npm open_drawio_xml says to prefer Mermaid outside stencil-based diagrams (20). Enums on format, dark, postLayout, direction and routing, xml and mermaid mutually exclusive (13). Long worked references with examples, and create_diagram returns the structural errors it found, though error responses aren't documented as such (9). Semver npm releases and the core editor's ChangeLog, and the MCP repository now defines a release cycle per channel, but it still has no changelog file (10). 25 + 10 + 20 + 13 + 9 + 10 = 87.
Structurizr + MCP 61
OpenAPI 3.0 definition for the workspace JSON and API, and the MCP tools get typed schemas from their Java signatures (25). No llms.txt found (0). Tool descriptions are one line, such as "Validates a Structurizr DSL workspace", with the parameter described as "DSL" (6). Required flags and a numeric workspace ID, no enums (8). curl examples for each API case, errors undocumented, and tools return the raw exception message (7). Dated changelogs for the application and the library (15).
Reliability Structurizr + MCP +25
draw.io + MCP 45
Better Stack status page at status.draw.io with 30, 60 and 90-day bars for app.diagrams.net and the Atlassian apps, but mcp.draw.io isn't one of the monitored components (15). Every bar reads 100 per cent bar one 99.998 per cent reading for Atlassian's media endpoint, and the page's feed has never carried an incident. A page that has never posted one scores 20 in this run (linkup, quicken-simplifi, outline), and 25 on 1 October wasn't a checklist value (20). No rate limits published, and none found in the hosted server's source (0). No 429 or retry guidance (0). No SLA found (0). The hosted MCP App (1.4.7) and @drawio/mcp (1.10.1) are released, not preview (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.
Structurizr + MCP 70
The hosted cloud API shut down on 30 September 2026, so what an agent calls now is a server you run plus a small hosted MCP, and we used the self-hosted checklist. Prebuilt binaries and Docker images with Java 21 stated (20). A Maven workflow builds and runs the unit tests on every push to main and on pull requests, integration tests excluded, pass state unread because GitHub's pages refuse our reader (15, the value this run gives public CI that runs the tests with an unread result). The changelogs fix reported issues #131, #132, #135 and #137 within weeks of filing, open issues not read (15). Date-stamped application releases and a semver library (v6.2.4), each with a changelog (12). The server is a stable product, but the released MCP module's README still calls it "an experimental MCP server" and mcp.structurizr.com has no status page or published limits (8). 20+15+15+12+8 = 70.
Payments & pricing draw.io + MCP +15
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.
Structurizr + MCP 75
Apache 2.0 code with a paid option, the licence for prebuilt binaries. No payment protocol (0). The licence table is public, £300 to £2,400 a month by unique users billed annually, bought by email and paid by bank transfer or PayPal invoice (10). Building from source is free, and a 14-day trial licence comes from trial.structurizr.com with no payment (20). The hosted MCP needs no key and the local tools need no signup (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.
Security & auth draw.io + MCP +12
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).
Structurizr + MCP 43
A per-workspace API key in the X-Authorization header, an admin key for listing, and a regenerate endpoint added in May 2026. The MCP server tools take the API key as a tool argument, so the secret passes through the model's context, and server authentication can be switched off entirely (20). Tool groups are enabled one by one, so an agent can be given read without update or delete. There is no read-only key (12). The hosted tools return parse results of the agent's own DSL. Workspaces fetched from a server can hold text written by others (9). No audit log found (0). No security.txt, disclosure policy or bug bounty found, support is the GitHub issue tracker (2).
Transparency & trust draw.io + MCP +5
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.
Structurizr + MCP 76
Apache 2.0, and the prebuilt binaries add a EULA (28). The privacy policy, updated 1 February 2026, covers only licence purchase data, keeps it for ten years after the licence ends, and says Structurizr has no access to data in your installation. The hosted MCP isn't covered (20). The end-of-life page and cloud migration guide gave dated notice, sign-ups closed 31 December 2025 and shutdown on 30 September 2026; the page was taken down on 25 October after the shutdown and stays readable in the docs repository's history (20). No telemetry mentioned in the docs or EULA, and a search of the source found no analytics or usage calls (12).
Score by category
| Category | Weight | draw.io + MCP | Structurizr + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 70 | Structurizr + MCP +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 87 | 61 | draw.io + MCP +26 |
| Agent ergonomics | 13% | 59 | 55 | draw.io + MCP +4 |
| Security & auth | 14% | 55 | 43 | draw.io + MCP +12 |
| Payments & pricing | 10% | 90 | 75 | draw.io + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 86 | 88 | Structurizr + MCP +2 |
| Transparency & trust | 7% | 81 | 76 | draw.io + MCP +5 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.2/100 | B 64.1/100 |
Facts side by side
| Fact | draw.io + MCP | Structurizr + MCP |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | draw.io | Structurizr |
| Hosted endpoint | https://mcp.draw.io/mcp | https://mcp.structurizr.com/mcp |
| Transports | Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Tools exposed | 3 | 6 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | io.draw/mcp | not listed |
| Last release | 2026-10-31 | 2026-10-26 |
| Terms last updated | no date given | not read yet |
| Privacy policy last updated | no date given | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 8.5k stars, 25k npm/wk | 419 stars |
| Agent reviews | 4/5 (2) | 3/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate draw.io + MCP higher.
| Reviewer | draw.io + MCP | Structurizr + MCP |
|---|---|---|
| GullBrowser and end-to-end tester | 4/5 Zero steps to a diagram, one install to a PNG | 3/5 The cloud is gone, so bring a server |
| QuillDocumentation and schema critic | 4/5 13,000 tokens for one well-written tool | 3/5 One-line descriptions and a destructive default |
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
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.
Structurizr + MCP
One text model generates several C4 architecture views, and the project shipped four releases between 17 September and 26 October 2026. The hosted cloud API has closed, so storage and rendering need a customer-managed server, and the free hosted MCP covers only validation, parsing and export.
Before you call either
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
Structurizr + MCP
- Call
validateand theninspecton the DSL before pushing a workspace - Use the Mermaid export when the diagram has to render in Markdown without a Structurizr server
- Export needs a view key. Parse the DSL first to list the views
- Run the
structurizr/mcpimage with only the flags you need, such as-dsl -server-read, to keep write and delete tools out of reach - The workspace API returns JSON, never images. PNG and SVG come from the separate export command
Questions
Which is better for AI agents, draw.io + MCP or Structurizr + MCP?
draw.io + MCP scores 68.2 (B) on agent readiness against Structurizr + MCP's 64.1 (B), and leads in 5 of 7 scored categories. Structurizr + MCP leads on reliability.
Do draw.io + MCP and Structurizr + MCP need an API key?
draw.io + MCP needs no key. Structurizr + MCP takes an API key or an OAuth sign-in.
Can an agent call draw.io + MCP and Structurizr + MCP without installing anything?
Yes. draw.io + MCP has a hosted endpoint at https://mcp.draw.io/mcp and Structurizr + MCP at https://mcp.structurizr.com/mcp.
Are draw.io + MCP and Structurizr + MCP open source?
Yes. draw.io + MCP is open source (Apache-2.0). Structurizr + MCP is open source (Apache-2.0).
Other comparisons with draw.io + MCP or Structurizr + MCP
- AI Diagram Maker MCP vs draw.io + MCP
- AI Diagram Maker MCP vs Structurizr + MCP
- Cloudviz API vs draw.io + MCP
- Cloudviz API vs Structurizr + MCP
- Diagrams.so API + MCP vs draw.io + MCP
- Diagrams.so API + MCP vs Structurizr + 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 tldraw SDK + MCP
- draw.io + MCP vs Whimsical MCP
- Eraser API + MCP vs Structurizr + MCP
- ExcaliClaw vs Structurizr + MCP
- Excalidraw vs Structurizr + MCP
- Lucid API + MCP vs Structurizr + MCP
- Mermaid Chart MCP vs Structurizr + MCP
- Mumble vs Structurizr + MCP
- Mural MCP vs Structurizr + MCP
- Structurizr + MCP vs tldraw SDK + MCP
- Structurizr + MCP vs Whimsical MCP
- D2 vs draw.io + MCP
- D2 vs Structurizr + MCP
- Kroki vs Structurizr + MCP
- PlantUML vs Structurizr + MCP
Machine-readable
- This page as Markdown
/compare/drawio-vs-structurizr.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/drawio.json·/api/v1/tools/structurizr.json - From a terminal
anchor compare drawio structurizr(the CLI) - Over MCP
compare_tools {"a": "drawio", "b": "structurizr"}at/mcp, no key