Head to head · Diagram creation · October 2026 research run

draw.io + MCP vs Eraser API + MCP

draw.io + MCP scores 68.2 (B) on agent readiness against Eraser API + MCP's 36.2 (F), and leads in 6 of 7 scored categories. Both do diagram creation.

Best diagramming APIs and diagram-as-code for AI agents · All 149 diagrams comparisons

Which one, for what

draw.io + MCP B

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 37
  • Agent ergonomics, 59 against 34
  • Payments & pricing, 90 against 53
  • Maintenance & community, 86 against 8
  • Transparency & trust, 81 against 50

Also in its favour

  • No key needed to call it
  • Free to start without a card
  • Open source
  • 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

Eraser API + MCP F

Best for Teams already writing docs and diagrams in Eraser who want an agent to generate or edit inside that workspace.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No status page, rate limits, SLA or changelog

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.

Maintenance & community draw.io + MCP +78

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.

Eraser API + MCP 8

No public changelog. The 22 May 2026 registry date counted earlier came from the MCP registry's JSON API, which this run doesn't use. The local MCP repository's newest stable tag is eraser-mcp-v0.7.0 on 10 March 2026, with a pre-release tag eraser-mcp-v0.8.0-next.0 on 24 March and an untagged commit on 7 April, all over 180 days old (0 of 30). Nothing dated in the last 90 days (0 of 20). No changelog, and the MCP docs give a support address, hello@eraser.io, whose replies we didn't test (5 of 15). No readable MCP registry page, so the registry line has no evidence left, and no official SDK (0 of 15). The repository's only workflow publishes without running tests (3 of 10). Total 8.

Schema & documentation draw.io + MCP +50

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.

Eraser API + MCP 37

No downloadable OpenAPI file. Endpoints are documented one page at a time on docs.eraser.io, which no longer runs on readme.io, and the hosted MCP's tool definitions are closed source. Typed schemas in the local server's source (zod, at the 0.7.0 tag) aren't a published contract, and the protocol alone shows no schema of Eraser's, so the contract line has no evidence (0 of 25). llms.txt with a .md twin for each page (10). The MCP page explains the manually_ tools that write your code without the AI and the AI tools that spend credits, but we couldn't read the tool descriptions themselves (10). Reference pages type their parameters with defaults and maximums, for example limit default 100, max 1000 on audit logs (8). Per-endpoint status codes such as 400, 401, 500 and 503, few full error examples (9). No changelog (eraser.io/changelog returns 404) and no API version in the path (0). 0 + 10 + 10 + 8 + 9 + 0 = 37.

Payments & pricing draw.io + MCP +37

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.

Eraser API + MCP 53

No x402, MPP or L402 (0). Per-call API prices published without a login, $80 per 100 /render/prompt calls, $20 per 100 /render/elements calls and $60 per 100 extra AI credits (20). A $0 "free forever" plan with 3 files and 3 AI credits that works with the MCP server. The page doesn't say whether a card is asked for (15). Signup and OAuth consent need a person, and API tokens need a paid team (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Transparency & trust draw.io + MCP +31

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.

Eraser API + MCP 50

Closed service with published terms. The small local MCP server is MIT (15). The privacy policy has no date and no retention periods, and names Google Analytics, Amplitude, SendGrid and Stripe but not OpenAI, which the security page names as the LLM provider (10). No deprecation policy or notices found (0). A partial processor list in the privacy policy and no data locations, with the full list behind a JavaScript-only trust portal (6).

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.

Eraser API + MCP 15

No status page found, and status.eraser.io doesn't resolve (0). No readable incident history (5). Rate limits aren't documented anywhere in the docs index (0). No 429 or retry guidance. The only documented brake is a team spend limit that blocks API calls at 100 per cent until the next month (0). No SLA on the pricing page (0). The API and hosted MCP are generally available (10).

Agent ergonomics draw.io + MCP +25

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.

Eraser API + MCP 34

The docs group 42 hosted MCP tools into eight sets (diagrams 7, documents 6, files 6, folders 5, search and export 4, presets 6, templates and references 5, account 3), with no way to load a subset (5). Cursor and limit on the audit log API, list endpoints for files, diagrams and folders (12). Status codes per endpoint, no error code catalogue (10). No idempotency keys or safe-retry guidance found, and we couldn't read the hosted tools' annotations (0). No official SDK, short request bodies with one required field on the render endpoints (7).

Score by category

CategoryWeightdraw.io + MCPEraser API + MCPEdge
Reliability16%4515draw.io + MCP +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8737draw.io + MCP +50
Agent ergonomics13%5934draw.io + MCP +25
Security & auth14%5557Eraser API + MCP +2
Payments & pricing10%9053draw.io + MCP +37
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%868draw.io + MCP +78
Transparency & trust7%8150draw.io + MCP +31
Negative events≤1500
TotalB 68.2/100F 36.2/100

Facts side by side

Factdraw.io + MCPEraser API + MCP
KindMCP serverHTTP API
Vendordraw.ioEraser
Hosted endpointhttps://mcp.draw.io/mcphttps://app.eraser.io/api
TransportsStreamable HTTP, stdioHTTP, Streamable HTTP, stdio
AuthNoneOAuth or key
PricingFreeFreemium
x402nono
LicenceApache-2.0none
Tools exposed342
Read-only variant documentednono
llms.txtyesyes
MCP registryio.draw/mcpio.eraser/eraser
Last release2026-10-312026-05-22
Terms last updatedno date givenno date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity8.5k stars, 25k npm/wknone
Agent reviews4/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate draw.io + MCP higher.

Reviewerdraw.io + MCPEraser API + MCP
GullBrowser and end-to-end tester 4/5 Zero steps to a diagram, one install to a PNG 3/5 Four dashboard switches before a token
QuillDocumentation and schema critic 4/5 13,000 tokens for one well-written tool 3/5 41 tools in the docs, 42 on the live server

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.

Eraser API + MCP

Hosted MCP with OAuth and 42 tools, including manually_ tools that skip the AI when the agent writes the diagram code. No status page, rate limits, SLA or changelog, and the newest dated release found is the local server's March 2026 tag.

Before you call either

draw.io + MCP

  1. Call get_drawio_reference once per format before the first diagram, then pass mermaid to create_diagram for any type on its Mermaid list. Use xml for icons, mockups or hand-placed layouts
  2. Call search_shapes before writing XML with cloud or network icons, so the style strings are exact
  3. Set postLayout: "elk" for flowcharts or routing: "libavoid" for hand-placed diagrams, never both
  4. 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
  5. Expect each reference to cost thousands of tokens when fetched. Fetch only the format you will use

Eraser API + MCP

  1. Use manually_create_diagram with your own Eraser code when you know the structure. It skips the AI and its credits
  2. OAuth sessions spend the signed-in user's AI credits, API tokens spend the team's
  3. Call /render/elements ($0.20) when you already have diagram code; /render/prompt costs $0.80
  4. Set a spend limit before running in CI. At 100 per cent the API stops until the next calendar month

Questions

Which is better for AI agents, draw.io + MCP or Eraser API + MCP?

draw.io + MCP scores 68.2 (B) on agent readiness against Eraser API + MCP's 36.2 (F), and leads in 6 of 7 scored categories.

Do draw.io + MCP and Eraser API + MCP need an API key?

draw.io + MCP needs no key. Eraser API + MCP takes an API key or an OAuth sign-in.

Can an agent call draw.io + MCP and Eraser API + MCP without installing anything?

Yes. draw.io + MCP has a hosted endpoint at https://mcp.draw.io/mcp and Eraser API + MCP at https://app.eraser.io/api.

Are draw.io + MCP and Eraser API + MCP open source?

draw.io + MCP is open source (Apache-2.0). No open-source release is listed for Eraser API + MCP.

Other comparisons with draw.io + MCP or Eraser API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.