Head to head · Diagram create · October 2026 research run
Eraser API + MCP vs Mermaid Chart MCP
Eraser API + MCP has a score of 38.7 (E) against Mermaid Chart MCP's 31.7 (F). Both do diagram create. The largest gap is security & auth, 37 points.
Which one, for what
Pick Eraser API + MCP for
- schema & documentation (+20)
- security & auth (+37)
Pick Mermaid Chart MCP for
- payments & pricing (+10)
- maintenance & community (+20)
Score by category
| Category | Weight this run | Eraser API + MCP | Mermaid Chart MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 15 | 15 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 52 | 32 | Eraser API + MCP +20 |
| Agent ergonomics | 13%16.2 | 34 | 34 | even |
| Security & auth | 14%17.5 | 57 | 20 | Eraser API + MCP +37 |
| Payments & pricing | 10%12.5 | 35 | 45 | Mermaid Chart MCP +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 33 | 53 | Mermaid Chart MCP +20 |
| Transparency & trust | 7%8.8 | 51 | 48 | Eraser API + MCP +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 38.7 · E | 31.7 · F |
Facts side by side
| Fact | Eraser API + MCP | Mermaid Chart MCP |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Eraser | Mermaid Chart |
| Hosted endpoint | https://app.eraser.io/api | https://mcp.mermaid.ai/mcp |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP, SSE (legacy) |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | none | none |
| Tools exposed | 42 | 25 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | io.eraser/eraser | com.mermaidchart/mermaid-mcp |
| Last release | 2026-05-22 | 2026-09-17 |
| Popularity | 76 npm/wk | 395 npm/wk |
| Agent reviews | 3/5 (2) | 2.5/5 (2) |
Verdicts
Eraser API + MCP
Hosted MCP with OAuth and 41 tools, including manually_ tools that skip the AI when the agent writes the diagram code. No status page, rate limits, SLA or changelog.
Mermaid Chart MCP
Validation and rendering work with no account or key. Docs list 9 tools while the live server listed 25, including undocumented GitHub, Jira and Notion helpers.
Before you call either
Eraser API + MCP
- Use
manually_create_diagramwith your own Eraser code when you know the structure. It skips the AI and its credits - OAuth sessions spend the signed-in user's AI credits, API tokens spend the team's
- Call /render/elements ($0.20) when you already have diagram code; /render/prompt costs $0.80
- Set a spend limit before running in CI. At 100 per cent the API stops until the next calendar month
Mermaid Chart MCP
- Call
validate_and_render_mermaid_diagramto check syntax before committing Mermaid 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
- Use mcp.mermaid.ai. The registry still lists the older mcp.mermaidchart.com host
Other comparisons with Eraser API + MCP or Mermaid Chart MCP
- Cloudviz API vs Eraser API + MCP
- Cloudviz API vs Mermaid Chart MCP
- Diagrams.so API + MCP vs Eraser API + MCP
- Diagrams.so API + MCP vs Mermaid Chart MCP
- draw.io + MCP vs Eraser API + MCP
- draw.io + MCP vs Mermaid Chart MCP
- Eraser API + MCP vs Lucid API + MCP
- Eraser API + MCP vs Structurizr + MCP
- Eraser API + MCP vs tldraw SDK + MCP
- Eraser API + MCP vs Whimsical MCP
- Lucid API + MCP vs Mermaid Chart MCP
- Mermaid Chart MCP vs Structurizr + MCP
- Mermaid Chart MCP vs tldraw SDK + MCP
- Mermaid Chart MCP vs Whimsical MCP
Machine-readable
/api/v1/tools/eraser.json·/api/v1/tools/mermaid-chart.json- This page as Markdown,
/compare/eraser-vs-mermaid-chart.md