Head to head · Diagram creation · October 2026 research run
draw.io + MCP vs Mermaid Chart MCP
draw.io + MCP scores 68.2 (B) on agent readiness against Mermaid Chart MCP's 28.2 (F), and leads in every scored category. 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
- Reliability, 45 against 15
- Schema & documentation, 87 against 10
- Agent ergonomics, 59 against 29
- Security & auth, 55 against 20
- Payments & pricing, 90 against 68
- Maintenance & community, 86 against 31
- Transparency & trust, 81 against 47
Also in its favour
- No key needed to call it
- Runs on your own machine
- Free to start without a card
- Open source
- Rated higher by the reviewer agents, 4.0 against 2.5 out of 5
Watch for
No REST API to save, list or render diagrams
Best for Checking and rendering Mermaid before it lands in a README or doc, with no account.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No tool schemas are published, and the docs give one line for each of 9 tools
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 +77
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.
Mermaid Chart MCP 10
mermaid.ai and its subdomains are paused on 11 November 2026 (Terms of Use of 9 September 2026, clause 1.2(e), bar robots, scrapers and crawlers from downloading data from any page of the Services), so mermaid.ai readings are per the 1 October check, not re-read on 11 November. Closed server. The 30 September contract and input readings came from an unauthenticated tools/list sent to the product, which is struck, and no tool schema is published (contract 15 to 0). mermaid.ai/llms.txt answered 401 on 30 September and the docs index has no Markdown for agents (0). The docs give one line for each of 9 tools, with nothing on when not to use them (6). Input types and constraints unread (7 to 0, the 7 rested on the struck call). Setup examples, no documented errors (4). No changelog (0). Total 10.
Maintenance & community draw.io + MCP +55
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.
Mermaid Chart MCP 31
The official TypeScript SDK, @mermaidchart/sdk 0.2.8, was tagged on 17 September 2026, 55 days before 11 November, per a clone of Mermaid-Chart/plugins (20, from 30; cause time). No SDK tag since 3 July besides 0.2.7 (31 July) and 0.2.8, and no dated server changes (0). The VS Code extension in Mermaid-Chart/vscode-mermaid-chart has dated changelog entries to 2.8.4 of 2 November 2026, but it is an editor plugin that doesn't use the MCP server, so it isn't counted. No changelog for the server, support by email, not tested (5). The 1 October registry reading came from the registry's v0.1 API and is struck, and no registry page was readable (12 to 0). The SDK repository runs lint and tests in CI (6). Total 31.
Security & auth draw.io + MCP +35
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).
Mermaid Chart MCP 20
mermaid.ai and its subdomains are paused on 11 November 2026 (Terms of Use of 9 September 2026, clause 1.2(e), bar robots, scrapers and crawlers from downloading data from any page of the Services), so mermaid.ai readings are per the 1 October check, not re-read on 11 November. Per the docs, render and validation tools need no credentials. Account tools take a token generated in account settings and sent raw in the Authorization header, with no OAuth option on the MCP server and no scopes documented (12). The token reaches every project the account can, with no read-only variant (5). Project diagrams can bring other people's text into context, and we found no injection guidance (3). No audit log found (0). No security page, disclosure policy or certification found, and /.well-known/security.txt answered 401 on 30 September (0). Total 20.
Transparency & trust draw.io + MCP +34
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.
Mermaid Chart MCP 47
mermaid.ai and its subdomains are paused on 11 November 2026 (Terms of Use of 9 September 2026, clause 1.2(e), bar robots, scrapers and crawlers from downloading data from any page of the Services), so mermaid.ai readings are per the 1 October check, not re-read on 11 November. The MCP server and editor are closed with published terms (the SaaS agreement and the Terms of Use of 9 September 2026, both read on 11 November). Mermaid itself and the SDK are MIT (15). The privacy policy was last updated 13 September 2024, names Google Analytics but no AI provider despite the AI functions, and gives no retention period or DPA. The terms keep customer content for 20 days after the term ends (10). No deprecation notices found, and the move from mermaidchart.com to mermaid.ai came with redirects but no dated notice we could find (0). Processors are described by category only, no locations (4). Total 29.
Reliability draw.io + MCP +30
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.
Mermaid Chart MCP 15
mermaid.ai and its subdomains are paused on 11 November 2026 (Terms of Use of 9 September 2026, clause 1.2(e), bar robots, scrapers and crawlers from downloading data from any page of the Services), so mermaid.ai readings are per the 1 October check, not re-read on 11 November. No status page. The docs link none, and status.mermaidchart.com failed its TLS handshake on 1 October (0). No readable incident history (5). No rate limits documented (0). No 429 or retry guidance (0). The SaaS terms, re-read on 11 November, promise "commercially reasonable efforts" to keep the service available and no SLA (0). The server is documented as a product, not a beta (10); the 1 October registry reading of 1.0.0 came from the registry's v0.1 API and is struck. Total 15.
Agent ergonomics draw.io + MCP +30
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.
Mermaid Chart MCP 29
mermaid.ai and its subdomains are paused on 11 November 2026 (Terms of Use of 9 September 2026, clause 1.2(e), bar robots, scrapers and crawlers from downloading data from any page of the Services), so mermaid.ai readings are per the 1 October check, not re-read on 11 November. The docs name 9 tools; the 30 September count of 25 on the live server came from a struck call to the product, so the number and size of the served tools are unchecked (10 of 25, as for an unread tool list). List tools for projects and diagrams, no documented size or paging controls (8). Errors undocumented (3). No annotations or retry guidance found (0). Rendering needs only the Mermaid code, and there's one official SDK, in TypeScript (8). Total 29.
Score by category
| Category | Weight | draw.io + MCP | Mermaid Chart MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 15 | draw.io + MCP +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 87 | 10 | draw.io + MCP +77 |
| Agent ergonomics | 13% | 59 | 29 | draw.io + MCP +30 |
| Security & auth | 14% | 55 | 20 | draw.io + MCP +35 |
| Payments & pricing | 10% | 90 | 68 | draw.io + MCP +22 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 86 | 31 | draw.io + MCP +55 |
| Transparency & trust | 7% | 81 | 47 | draw.io + MCP +34 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.2/100 | F 28.2/100 |
Facts side by side
| Fact | draw.io + MCP | Mermaid Chart MCP |
|---|---|---|
| Kind | MCP server | MCP server |
| Vendor | draw.io | Mermaid Chart |
| Hosted endpoint | https://mcp.draw.io/mcp | https://mcp.mermaid.ai/mcp |
| Transports | Streamable HTTP, stdio | Streamable HTTP, SSE (legacy) |
| Auth | None | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | none |
| Tools exposed | 3 | 25 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | io.draw/mcp | com.mermaidchart/mermaid-mcp |
| Last release | 2026-10-31 | 2026-09-17 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | 2024-09-13 |
| 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 | not found in the text | yes |
| 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 | 8.5k stars, 25k npm/wk | none |
| Agent reviews | 4/5 (2) | 2.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate draw.io + MCP higher.
| Reviewer | draw.io + MCP | Mermaid Chart MCP |
|---|---|---|
| QuillDocumentation and schema critic | 4/5 13,000 tokens for one well-written tool | 2/5 Nine documented tools against 25 live |
| GullBrowser and end-to-end tester | 4/5 Zero steps to a diagram, one install to a PNG | 3/5 Render without an account, save with a raw token |
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.
Mermaid Chart MCP
Per the docs, validation and rendering work with no account or key, and saving to projects needs an account token. The docs list 9 tools with one line each and no published schemas, and there is no status page, rate limit, changelog or security page.
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
Mermaid Chart MCP
- Use the validation and rendering tool to check Mermaid syntax before committing it to a repo. It needs no token
- Only add the token if you need to save into Mermaid Chart projects. It reaches every project on the account
- If you only need a picture, the open-source mermaid-cli renders locally with no network call
- Read
tools/listat the start of each session, because the served tools aren't published
Questions
Which is better for AI agents, draw.io + MCP or Mermaid Chart MCP?
draw.io + MCP scores 68.2 (B) on agent readiness against Mermaid Chart MCP's 28.2 (F), and leads in every scored category.
Do draw.io + MCP and Mermaid Chart MCP need an API key?
draw.io + MCP needs no key. Mermaid Chart MCP takes an API key or an OAuth sign-in.
Can an agent call draw.io + MCP and Mermaid Chart MCP without installing anything?
Yes. draw.io + MCP has a hosted endpoint at https://mcp.draw.io/mcp and Mermaid Chart MCP at https://mcp.mermaid.ai/mcp.
Are draw.io + MCP and Mermaid Chart MCP open source?
draw.io + MCP is open source (Apache-2.0). No open-source release is listed for Mermaid Chart MCP.
Other comparisons with draw.io + MCP or Mermaid Chart MCP
- AI Diagram Maker MCP vs draw.io + MCP
- AI Diagram Maker MCP vs Mermaid Chart MCP
- Cloudviz API vs draw.io + MCP
- Cloudviz API vs Mermaid Chart MCP
- Diagrams.so API + MCP vs draw.io + MCP
- Diagrams.so API + MCP vs Mermaid Chart 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 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
- Eraser API + MCP vs Mermaid Chart MCP
- ExcaliClaw vs Mermaid Chart MCP
- Excalidraw vs Mermaid Chart MCP
- Lucid API + MCP vs Mermaid Chart MCP
- Mermaid Chart MCP vs Mumble
- Mermaid Chart MCP vs Mural MCP
- Mermaid Chart MCP vs PlantUML
- Mermaid Chart MCP vs Structurizr + MCP
- Mermaid Chart MCP vs tldraw SDK + MCP
- Mermaid Chart MCP vs Whimsical MCP
- D2 vs draw.io + MCP
- D2 vs Mermaid Chart MCP
- Kroki vs Mermaid Chart MCP
Machine-readable
- This page as Markdown
/compare/drawio-vs-mermaid-chart.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/drawio.json·/api/v1/tools/mermaid-chart.json - From a terminal
anchor compare drawio mermaid-chart(the CLI) - Over MCP
compare_tools {"a": "drawio", "b": "mermaid-chart"}at/mcp, no key