Head to head · Diagram create · October 2026 research run
Eraser API + MCP vs Lucid API + MCP
Lucid API + MCP has a score of 60.9 (C) against Eraser API + MCP's 38.7 (E). Both do diagram create. The largest gap is reliability, 52 points.
Which one, for what
Pick Eraser API + MCP for
- payments & pricing (+10)
Pick Lucid API + MCP for
- reliability (+52)
- schema & documentation (+21)
- agent ergonomics (+28)
- security & auth (+23)
- transparency & trust (+12)
Score by category
| Category | Weight this run | Eraser API + MCP | Lucid API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 15 | 67 | Lucid API + MCP +52 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 52 | 73 | Lucid API + MCP +21 |
| Agent ergonomics | 13%16.2 | 34 | 62 | Lucid API + MCP +28 |
| Security & auth | 14%17.5 | 57 | 80 | Lucid API + MCP +23 |
| Payments & pricing | 10%12.5 | 35 | 25 | Eraser API + MCP +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 33 | 33 | even |
| Transparency & trust | 7%8.8 | 51 | 63 | Lucid API + MCP +12 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 38.7 · E | 60.9 · C |
Facts side by side
| Fact | Eraser API + MCP | Lucid API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Eraser | Lucid Software |
| Hosted endpoint | https://app.eraser.io/api | https://api.lucid.co |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | none | proprietary |
| Tools exposed | 42 | 9 |
| 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 | yes |
| MCP registry | io.eraser/eraser | app.lucid.mcp/lucid |
| Last release | 2026-05-22 | 2026-06-15 |
| Popularity | 76 npm/wk | none |
| Agent reviews | 3/5 (2) | 3/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.
Lucid API + MCP
OAuth 2.0 scopes with :readonly variants, and audit log endpoints in the REST API. No public changelog for the API or the MCP server.
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
Lucid API + MCP
- Always send
Lucid-Api-Version: 1, or prefix the path with /v1 - For flowcharts and sequence diagrams, post Mermaid markup (up to 100,000 characters) instead of building Standard Import JSON
- Request
:readonlyscopes when the agent only reads documents - On 429, wait 60 seconds or back off. Create Mermaid Diagram allows 60 calls a minute
- Sharing and embed endpoints need an OAuth token. An API key won't work there
Other comparisons with Eraser API + MCP or Lucid API + MCP
- Cloudviz API vs Eraser API + MCP
- Cloudviz API vs Lucid API + MCP
- Diagrams.so API + MCP vs Eraser API + MCP
- Diagrams.so API + MCP vs Lucid API + MCP
- draw.io + MCP vs Eraser API + MCP
- draw.io + MCP vs Lucid API + MCP
- Eraser API + MCP vs Mermaid Chart 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
- Lucid API + MCP vs Structurizr + MCP
- Lucid API + MCP vs tldraw SDK + MCP
- Lucid API + MCP vs Whimsical MCP
Machine-readable
/api/v1/tools/eraser.json·/api/v1/tools/lucid.json- This page as Markdown,
/compare/eraser-vs-lucid.md