Head to head · Diagram creation · October 2026 research run

draw.io + MCP vs Whimsical MCP

draw.io + MCP scores 68.2 (B) on agent readiness against Whimsical MCP's 52.1 (D), and leads in 5 of 7 scored categories. Whimsical 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

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

  • Schema & documentation, 87 against 54
  • Agent ergonomics, 59 against 46
  • Payments & pricing, 90 against 38
  • Maintenance & community, 86 against 31
  • Transparency & trust, 81 against 71

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 3.0 out of 5

Watch for

No REST API to save, list or render diagrams

Whimsical MCP D

Best for A person who already uses Whimsical and wants an agent to draft flowcharts, mind maps or wireframes into the shared workspace.

Ahead on

  • Reliability, 60 against 45

Watch for

No API keys, so it can't run headless or in CI

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 +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.

Whimsical MCP 31

The newest dated release is the repository's v1.1.0 tag (server.json and plugin manifests 1.1.0) of 8 September 2026, 57 days before 4 November (20). The commits of 14 October rewrite the README, add screenshots and glama.json and change a contact email, with no version, so they don't count. One dated release since 6 August, and the registry's 13 August date for 1.0.0 came from its JSON API and is struck, so the 90-day line stays 0. The changelog page wasn't re-read (terms ban). Support by email, not tested (8). The README says the server is listed in the official MCP Registry as com.whimsical/mcp, and its server.json names that entry, but that is Whimsical's own claim. The registry's listing can only be read through its JSON API, which this benchmark doesn't use, so presence is unread (0, as copilot-studio-mcp and linear-mcp). The public repo holds only a guide and manifests, nothing to build or test (3). 20 + 0 + 8 + 0 + 3 = 31.

Payments & pricing draw.io + MCP +52

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.

Whimsical MCP 38

No x402, MPP or L402 (0). Plan prices are public per the 30 September check, Pro $10 and Business $20 per editor a month billed yearly, nothing per call (10, per the 1 October check, not re-read on 4 November because Whimsical's terms bar robots and other automatic means of access). A $0 Free plan on which every MCP tool works, capped at 50 board objects a month, restated in the README of 14 October 2026. We couldn't confirm the Free plan takes no card (15). OAuth sign-in needs a person (0). 0 + 10 + 15 + 0 = 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Schema & documentation draw.io + MCP +33

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.

Whimsical MCP 54

The server is closed, so we couldn't read the tool schemas. MCP requires typed inputs, and the tool spec page documented each tool on 1 October (15, per the 1 October check, not re-read on 4 November because Whimsical's terms bar robots and other automatic means of access). No llms.txt. The how_to tool hands the agent Whimsical's syntax docs on demand (5). Whimsical's README of 14 October 2026 gives one line of purpose for each of its 14 tools, without when-not-to-use guidance (12). Input constraints unread (7). No documented error responses beyond the README's 401 troubleshooting (5). Versioning through the registry manifest (server.json 1.0.0 from 26 March 2026, 1.1.0 tagged v1.1.0 on 8 September 2026), and a changelog page that needed JavaScript on 1 October and isn't re-read (10). 15 + 5 + 12 + 7 + 5 + 10 = 54.

Reliability Whimsical MCP +15

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.

Whimsical MCP 60

Status page at status.whimsical.com, run on Sorry, with a history page (20), per the 1 October check, not re-read on 4 November because Whimsical's terms bar robots and other automatic means of access. The last incident it showed was on 6 March 2026, so the window read on 1 October was clean. The part from 2 October to 4 November is unread and earns nothing new, so the line keeps its 1 October award (30). Rate limits aren't documented, and the README of 14 October 2026 names no limit (0). No 429 or retry guidance. The README's troubleshooting covers only 401 and expired sessions (0). No SLA found (0). The remote MCP server is generally available, tagged v1.1.0 in Whimsical's repository (10). 20 + 30 + 0 + 0 + 0 + 10 = 60.

Agent ergonomics draw.io + MCP +13

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.

Whimsical MCP 46

14 tools in the README's tool table of 14 October 2026 (11 to 30, 15), with syntax docs loaded on demand through how_to (3 back, 18). search filters by text, creation date or update date, file_tree and fetch scope what comes back, and fetch can return a PNG snapshot (10). Error responses aren't documented (5). Read and write tools are separate, and we couldn't read the readOnlyHint or destructiveHint annotations on the live server (5). add_board_content lays out flowcharts, mind maps and sequence diagrams automatically and auto_layout re-runs the layout, no SDK (8). 18 + 10 + 5 + 5 + 8 = 46.

Transparency & trust draw.io + MCP +10

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.

Whimsical MCP 71

The server is closed with published terms, last updated 30 July 2025. The MIT licence on GitHub covers a setup guide and manifests, not the server (15). Privacy policy from August 2025 with a DPA, US hosting with Standard Contractual Clauses for transfers, AI supplementary terms, and no retention periods in days (22, per the 1 October check, not re-read on 4 November because Whimsical's terms bar robots and other automatic means of access). No deprecation policy or dated notices found, and the REST API is still a closed beta (0). A separate subprocessor list, and hosting in the US named (16). 15 + 22 + 0 + 16 = 53.

Score by category

CategoryWeightdraw.io + MCPWhimsical MCPEdge
Reliability16%4560Whimsical MCP +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8754draw.io + MCP +33
Agent ergonomics13%5946draw.io + MCP +13
Security & auth14%5558Whimsical MCP +3
Payments & pricing10%9038draw.io + MCP +52
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8631draw.io + MCP +55
Transparency & trust7%8171draw.io + MCP +10
Negative events≤1500
TotalB 68.2/100D 52.1/100

Facts side by side

Factdraw.io + MCPWhimsical MCP
KindMCP serverMCP server
Vendordraw.ioWhimsical
Hosted endpointhttps://mcp.draw.io/mcphttps://mcp.whimsical.com/mcp
TransportsStreamable HTTP, stdioStreamable HTTP
AuthNoneOAuth
PricingFreeFreemium
x402nono
LicenceApache-2.0proprietary
Tools exposed314
Read-only variant documentednono
llms.txtyesno
MCP registryio.draw/mcpcom.whimsical/mcp
Last release2026-10-312026-09-08
Terms last updatedno date given2025-07-30
Privacy policy last updatedno date given2025-08-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
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 textyes
Popularity8.5k stars, 25k npm/wk5 stars
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 + MCPWhimsical MCP
GullBrowser and end-to-end tester 4/5 Zero steps to a diagram, one install to a PNG 3/5 OAuth or nothing
QuillDocumentation and schema critic 4/5 13,000 tokens for one well-written tool 3/5 Three tool counts and a syntax tool on demand

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.

Whimsical MCP

OAuth 2.1 with PKCE and separate read and write scopes. No API keys, so it can't run headless or in CI.

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

Whimsical MCP

  1. Use add_board_content for flowcharts, mind maps, sequence diagrams and wireframes, and auto_layout to change direction, rather than placing shapes one by one with edit
  2. Call how_to for Whimsical's syntax before writing a large flowchart or wireframe
  3. Use fetch when you need a PNG snapshot of a board
  4. delete moves files to the trash, and edit and comment_edit can delete content, without asking. Confirm with the person first
  5. On a 401 or "Missing Bearer token" answer, ask the person to sign in again through the client's reconnect action

Questions

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

draw.io + MCP scores 68.2 (B) on agent readiness against Whimsical MCP's 52.1 (D), and leads in 5 of 7 scored categories. Whimsical MCP leads on reliability.

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

draw.io + MCP needs no key. Whimsical MCP uses an OAuth sign-in.

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

Yes. draw.io + MCP has a hosted endpoint at https://mcp.draw.io/mcp and Whimsical MCP at https://mcp.whimsical.com/mcp.

Are draw.io + MCP and Whimsical MCP open source?

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

Other comparisons with draw.io + MCP or Whimsical 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.