Head to head · Diagram creation · October 2026 research run

Eraser API + MCP vs Whimsical MCP

Whimsical MCP scores 52.1 (D) on agent readiness against Eraser API + MCP's 36.2 (F), and leads in 6 of 7 scored categories. Eraser API + MCP leads on payments & pricing. Both do diagram creation.

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

Which one, for what

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.

Ahead on

  • Payments & pricing, 53 against 38

Also in its favour

  • Runs on your own machine

Watch for

No status page, rate limits, SLA or changelog

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 15
  • Schema & documentation, 54 against 37
  • Agent ergonomics, 46 against 34
  • Maintenance & community, 31 against 8
  • Transparency & trust, 71 against 50

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.

Reliability Whimsical MCP +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).

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.

Maintenance & community Whimsical MCP +23

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.

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.

Transparency & trust Whimsical MCP +21

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

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.

Schema & documentation Whimsical MCP +17

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.

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.

Payments & pricing Eraser API + MCP +15

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.

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.

Agent ergonomics Whimsical MCP +12

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

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.

Score by category

CategoryWeightEraser API + MCPWhimsical MCPEdge
Reliability16%1560Whimsical MCP +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3754Whimsical MCP +17
Agent ergonomics13%3446Whimsical MCP +12
Security & auth14%5758Whimsical MCP +1
Payments & pricing10%5338Eraser API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%831Whimsical MCP +23
Transparency & trust7%5071Whimsical MCP +21
Negative events≤1500
TotalF 36.2/100D 52.1/100

Facts side by side

FactEraser API + MCPWhimsical MCP
KindHTTP APIMCP server
VendorEraserWhimsical
Hosted endpointhttps://app.eraser.io/apihttps://mcp.whimsical.com/mcp
TransportsHTTP, Streamable HTTP, stdioStreamable HTTP
AuthOAuth or keyOAuth
PricingFreemiumFreemium
x402nono
Licencenoneproprietary
Tools exposed4214
Read-only variant documentednono
llms.txtyesno
MCP registryio.eraser/erasercom.whimsical/mcp
Last release2026-05-222026-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
Popularitynone5 stars
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

ReviewerEraser API + MCPWhimsical MCP
GullBrowser and end-to-end tester 3/5 Four dashboard switches before a token 3/5 OAuth or nothing
QuillDocumentation and schema critic 3/5 41 tools in the docs, 42 on the live server 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

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.

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

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

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, Eraser API + MCP or Whimsical MCP?

Whimsical MCP scores 52.1 (D) on agent readiness against Eraser API + MCP's 36.2 (F), and leads in 6 of 7 scored categories. Eraser API + MCP leads on payments & pricing.

Do Eraser API + MCP and Whimsical MCP need an API key?

Eraser API + MCP takes an API key or an OAuth sign-in. Whimsical MCP uses an OAuth sign-in.

Can an agent call Eraser API + MCP and Whimsical MCP without installing anything?

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

Other comparisons with Eraser API + 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.