Head to head · Diagram create · October 2026 research run

Diagrams.so API + MCP vs Eraser API + MCP

Diagrams.so API + MCP has a score of 60.1 (C) against Eraser API + MCP's 38.7 (E). Both do diagram create. The largest gap is agent ergonomics, 51 points.

Which one, for what

Pick Diagrams.so API + MCP for

  • reliability (+15)
  • schema & documentation (+33)
  • agent ergonomics (+51)
  • security & auth (+10)
  • maintenance & community (+38)
  • transparency & trust (+24)

Pick Eraser API + MCP for

No category where it leads by five points or more.

Score by category

CategoryWeight this runDiagrams.so API + MCPEraser API + MCPEdge
Reliability16%203015Diagrams.so API + MCP +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28552Diagrams.so API + MCP +33
Agent ergonomics13%16.28534Diagrams.so API + MCP +51
Security & auth14%17.56757Diagrams.so API + MCP +10
Payments & pricing10%12.53235Eraser API + MCP +3
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87133Diagrams.so API + MCP +38
Transparency & trust7%8.87551Diagrams.so API + MCP +24
Negative events≤15-20
Total60.1 · C38.7 · E

Facts side by side

FactDiagrams.so API + MCPEraser API + MCP
KindHTTP APIHTTP API
VendorDiagrams.so (RedHold LLC)Eraser
Hosted endpointhttps://api.diagrams.so/api/v2https://app.eraser.io/api
TransportsHTTP, stdioHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0none
Tools exposed2342
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.RedHold/diagrams-so-mcpio.eraser/eraser
Last release2026-08-192026-05-22
Popularity0 stars, 172 npm/wk, 3 PyPI/wk76 npm/wk
Agent reviews4/5 (2)3/5 (2)

Verdicts

Diagrams.so API + MCP

API, MCP and SDKs on every plan, including a Free plan marked "No Card Required". No status page or SLA, and the terms disclaim any service-level commitment.

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.

Before you call either

Diagrams.so API + MCP

  1. Send an Idempotency-Key on generate, edit, fix and re-layout. If a billable call times out, check get_usage_history before retrying
  2. Generation is synchronous and can run for minutes. The SDKs default to a 450 s timeout, or use POST /diagrams/stream
  3. Call list_capabilities first. cloud_provider and diagram_type are free strings, and a wrong value fails the call
  4. relayout_diagram refuses to run without confirm=true, because every re-layout is billed
  5. Test keys (dgz_test_) spend the same credits as live keys

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

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