Head to head · Diagram creation · October 2026 research run

Eraser API + MCP vs Lucid API + MCP

Lucid API + MCP scores 65 (B) 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

Best design workspace and canvas APIs for AI agents · All 162 design 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

Lucid API + MCP B

Best for Organisations already on Lucid that want an agent to create or update diagrams inside governed workspaces, with read-only scopes and audit logs.

Ahead on

  • Reliability, 80 against 15
  • Schema & documentation, 73 against 37
  • Agent ergonomics, 62 against 34
  • Security & auth, 80 against 57
  • Maintenance & community, 33 against 8
  • Transparency & trust, 62 against 50

Watch for

No public changelog for the API or the MCP server

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 Lucid API + MCP +65

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

Lucid API + MCP 80

Atlassian Statuspage at status.lucid.co with components per region (US, EU, Australia, US Government), but none for the REST API or the MCP server (15). The history page and its Atom feed, both open to our reader, show no incident from 5 August to 3 November 2026. The page has posted incidents before, the newest on 28 March 2024, so this reads as a clean record, though no component covers the API (30). Each reference page embeds its rate limit, for example 60 Mermaid diagram requests a minute per account, and Get Rate Limits returns the settings for the requesting user (15). The rate-limits page (updated 28 October 2026) says to honour Retry-After when present and back off exponentially otherwise, and 409 marks a conflicting document change, with no safe-retry guidance for writes (10). No SLA found (0). The REST API is generally available and the MCP server is at 1.0.0 in the official registry since 15 June 2026 (10). 15+30+15+10+0+10 = 80.

Schema & documentation Lucid API + MCP +36

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.

Lucid API + MCP 73

Each reference page embeds an OpenAPI 3.0.3 fragment for its operation with server https://api.lucid.co, but there's no single spec file to download (20). llms.txt and a .md twin of every reference page (10). Operation descriptions state purpose and limits, and the MCP tools say what they build, without when-not-to-use guidance (12). Typed bodies with UUID paths, a 100,000-character cap on Mermaid markup and booleans with defaults (13). Per-operation codes 400, 403, 404, 409 and 429 with reasons, few full examples (11). A required Lucid-Api-Version header, but no public changelog (the readme.io changelog returns 404) (7).

Agent ergonomics Lucid API + MCP +28

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

Lucid API + MCP 62

Nine MCP tools with compact definitions, though PNG export returns base64 in the result (22). Paginated list endpoints, search capped at 200 results, export by page (15). Status codes on every operation with the cause of each (15). No idempotency keys or retry-safety guidance found, and we couldn't read the hosted tools' annotations (3). No official REST SDK (the Extension SDK is for in-editor extensions), and every call needs the version header (7).

Maintenance & community Lucid API + MCP +25

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.

Lucid API + MCP 33

No public changelog for the REST API or the MCP server. The newest dated change is the MCP server's 1.0.0 registry entry of 15 June 2026, 141 days before the check (10). No dated release or change in the 90 days from 5 August. Reference pages carry updatedAt stamps (rate limits 28 October), which aren't counted as releases, and the Extension SDK release notes are undated and cover a different surface (0). Support at support@lucid.co and a community forum with developer announcements, not tested (8). In the official MCP registry as app.lucid.mcp/lucid under Lucid's own domain (15). No official REST SDK package to assess (0). 10+0+8+15+0 = 33.

Security & auth Lucid API + MCP +23

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

Lucid API + MCP 80

OAuth 2.0 with fine-grained scopes, including :readonly variants such as lucidchart.document.content:readonly, plus API keys limited by grants such as DocumentEdit. The MCP server uses OAuth with dynamic client registration (28). Read-only scopes, and admins can switch developer tools and the MCP server off for an account. Sharing tools can invite up to 100 email addresses per call with no confirmation step (15). Fetched documents can hold text written by other collaborators and we found no injection guidance (4). Get and Query Audit Logs endpoints in the REST API (15). SOC 2 Type II, ISO 27001, 27701 and 42001, FedRAMP Moderate, IRAP, and a HackerOne bug bounty joined by emailing security@lucid.co. No security.txt per the 30 September check (18).

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.

Lucid API + MCP 38

No x402, MPP or L402 (0). Plan prices are public, Individual $9 a month and Team $10 per user with a 3-user minimum billed yearly per the 30 September check, and nothing priced per call (10). A Free plan exists. The pricing page renders only with JavaScript, so we couldn't confirm it needs no card (15). Signup, developer-tool activation and OAuth consent all need a person (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Score by category

CategoryWeightEraser API + MCPLucid API + MCPEdge
Reliability16%1580Lucid API + MCP +65
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3773Lucid API + MCP +36
Agent ergonomics13%3462Lucid API + MCP +28
Security & auth14%5780Lucid API + MCP +23
Payments & pricing10%5338Eraser API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%833Lucid API + MCP +25
Transparency & trust7%5062Lucid API + MCP +12
Negative events≤1500
TotalF 36.2/100B 65/100

Facts side by side

FactEraser API + MCPLucid API + MCP
KindHTTP APIHTTP API
VendorEraserLucid Software
Hosted endpointhttps://app.eraser.io/apihttps://api.lucid.co
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
Licencenoneproprietary
Tools exposed429
Read-only variant documentednono
llms.txtyesyes
MCP registryio.eraser/eraserapp.lucid.mcp/lucid
Last release2026-05-222026-06-15
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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.

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

  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

Lucid API + MCP

  1. Always send Lucid-Api-Version: 1, or prefix the path with /v1
  2. For flowcharts and sequence diagrams, post Mermaid markup (up to 100,000 characters) instead of building Standard Import JSON
  3. Request :readonly scopes when the agent only reads documents
  4. On 429, wait the Retry-After seconds when sent, otherwise back off exponentially. Mermaid diagram calls share 60 requests a minute per account
  5. Sharing and embed endpoints need an OAuth token. An API key won't work there

Questions

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

Lucid API + MCP scores 65 (B) 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 Lucid API + MCP need an API key?

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

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

Yes. Eraser API + MCP has a hosted endpoint at https://app.eraser.io/api and Lucid API + MCP at https://api.lucid.co.

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