Head to head · Diagram creation · October 2026 research run

Eraser API + MCP vs Mermaid Chart MCP

Eraser API + MCP scores 36.2 (F) on agent readiness against Mermaid Chart MCP's 28.2 (F), and leads in 4 of 7 scored categories. Mermaid Chart MCP leads on payments & pricing and maintenance & community. 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

  • Schema & documentation, 37 against 10
  • Agent ergonomics, 34 against 29
  • Security & auth, 57 against 20

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

No status page, rate limits, SLA or changelog

Mermaid Chart MCP F

Best for Checking and rendering Mermaid before it lands in a README or doc, with no account.

Ahead on

  • Payments & pricing, 68 against 53
  • Maintenance & community, 31 against 8

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.

Security & auth Eraser API + MCP +37

Eraser API + MCP 57

Hosted MCP signs in with OAuth by default. The REST API takes one Bearer token per team, issued only to paid teams, with no scopes documented; deleting a token stops it at once, and organisation tokens act on every team in an organisation. Audit logs need a separate tenant-level key (22). OAuth-created files are private by default and files are archived rather than deleted, though diagrams and folders have delete endpoints, and there's no read-only token (8). Tools return team documents, diagrams and connected git and cloud data, and we found no prompt-injection guidance (3). An audit log API on Enterprise with ECS and Splunk CIM formats, plus a team usage endpoint (12). SOC 2 Type 2 and a penetration test report through the trust portal. No security.txt per the 30 September check, no bug bounty found (12).

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.

Schema & documentation Eraser API + MCP +27

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.

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 Mermaid Chart 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.

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.

Payments & pricing Mermaid Chart 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.

Mermaid Chart MCP 68

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 x402, MPP or L402 (0). Plan prices per the 30 September check, Plus $12 and Premium $24 a user a month billed monthly, nothing per call. The pricing page needs JavaScript and didn't render for us on 1 October (10). Rendering and validation are free with no account (20). An agent can render and validate without any signup, but saving to projects needs a person to create an account and token (15). Total 45. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 45 is 68.

Agent ergonomics Eraser API + MCP +5

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

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

CategoryWeightEraser API + MCPMermaid Chart MCPEdge
Reliability16%1515even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3710Eraser API + MCP +27
Agent ergonomics13%3429Eraser API + MCP +5
Security & auth14%5720Eraser API + MCP +37
Payments & pricing10%5368Mermaid Chart MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%831Mermaid Chart MCP +23
Transparency & trust7%5047Eraser API + MCP +3
Negative events≤1500
TotalF 36.2/100F 28.2/100

Facts side by side

FactEraser API + MCPMermaid Chart MCP
KindHTTP APIMCP server
VendorEraserMermaid Chart
Hosted endpointhttps://app.eraser.io/apihttps://mcp.mermaid.ai/mcp
TransportsHTTP, Streamable HTTP, stdioStreamable HTTP, SSE (legacy)
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
Tools exposed4225
Read-only variant documentednono
llms.txtyesno
MCP registryio.eraser/erasercom.mermaidchart/mermaid-mcp
Last release2026-05-222026-09-17
Terms last updatedno date givenno date given
Privacy policy last updatedno date given2024-09-13
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 textyes
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
Agent reviews3/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Eraser API + MCP higher.

ReviewerEraser API + MCPMermaid Chart MCP
QuillDocumentation and schema critic 3/5 41 tools in the docs, 42 on the live server 2/5 Nine documented tools against 25 live
GullBrowser and end-to-end tester 3/5 Four dashboard switches before a token 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

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.

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

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

Mermaid Chart MCP

  1. Use the validation and rendering tool to check Mermaid syntax before committing it to a repo. It needs no token
  2. Only add the token if you need to save into Mermaid Chart projects. It reaches every project on the account
  3. If you only need a picture, the open-source mermaid-cli renders locally with no network call
  4. Read tools/list at the start of each session, because the served tools aren't published

Questions

Which is better for AI agents, Eraser API + MCP or Mermaid Chart MCP?

Eraser API + MCP scores 36.2 (F) on agent readiness against Mermaid Chart MCP's 28.2 (F), and leads in 4 of 7 scored categories. Mermaid Chart MCP leads on payments & pricing and maintenance & community.

Do Eraser API + MCP and Mermaid Chart MCP need an API key?

Both take an API key or an OAuth sign-in.

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

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

Other comparisons with Eraser API + MCP or Mermaid Chart 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.