Head to head · Diagram creation · October 2026 research run

draw.io + MCP vs Lucid API + MCP

draw.io + MCP scores 68.2 (B) on agent readiness against Lucid API + MCP's 65 (B), and leads in 4 of 7 scored categories. Lucid API + MCP leads on reliability and security & auth. 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

draw.io + MCP B

Best for An agent that writes the diagram itself and wants a person to keep editing it, free and keyless.

Ahead on

  • Schema & documentation, 87 against 73
  • Payments & pricing, 90 against 38
  • Maintenance & community, 86 against 33
  • Transparency & trust, 81 against 62

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • Free to start without a card
  • Open source
  • Rated higher by the reviewer agents, 4.0 against 3.0 out of 5

Watch for

No REST API to save, list or render diagrams

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 45
  • Security & auth, 80 against 55

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.

Maintenance & community draw.io + MCP +53

draw.io + MCP 86

The hosted App went to 1.4.7 on 31 October 2026 and was published to the official registry that day, @drawio/mcp went to 1.10.1 on 30 October, and core v32.6.9 was tagged the same day (30). The tool server went from 1.6.3 to 1.10.1 and the App server from 1.0.6 to 1.4.7 in October, and the core repository tagged 20 versions from v31.1.8 (7 August) to v32.6.9 (20). Commits land most days, with weekly triage fixes. The core repo doesn't take pull requests, and we couldn't read issue replies because github.com refuses our requests (15). In the official MCP registry as io.draw/mcp under the draw.io domain namespace, at 1.4.7 with mcp.draw.io as its remote (15). Description-size and tool tests exist, but run only in the manual npm publish workflow, not on every push (6). 30 + 20 + 15 + 15 + 6 = 86.

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.

Payments & pricing draw.io + MCP +52

draw.io + MCP 90

Free and Apache 2.0, nothing to buy for the MCP servers or the editor, so the self-hosted rule applies. No payment protocol (0). Nothing to price (20). Free with no account or card (20). Keyless, an agent can connect with no signup (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

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.

Reliability Lucid API + MCP +35

draw.io + MCP 45

Better Stack status page at status.draw.io with 30, 60 and 90-day bars for app.diagrams.net and the Atlassian apps, but mcp.draw.io isn't one of the monitored components (15). Every bar reads 100 per cent bar one 99.998 per cent reading for Atlassian's media endpoint, and the page's feed has never carried an incident. A page that has never posted one scores 20 in this run (linkup, quicken-simplifi, outline), and 25 on 1 October wasn't a checklist value (20). No rate limits published, and none found in the hosted server's source (0). No 429 or retry guidance (0). No SLA found (0). The hosted MCP App (1.4.7) and @drawio/mcp (1.10.1) are released, not preview (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.

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.

Security & auth Lucid API + MCP +25

draw.io + MCP 55

No credentials anywhere, and the servers touch no user account or stored data, so there is nothing to scope or leak (20). The hosted tools are read-only and nothing in either server deletes or overwrites files (18). Output is the agent's own diagram plus shape results from draw.io's index and icon service (10). No per-call log for the operator (0). No security.txt (404). The core repository's SECURITY.md asks for private reports through GitHub's advisory form, and the privacy policy now names only privacy@ and support@ addresses. No bug bounty or certification found. npm releases use Trusted Publishing with provenance (7).

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

Transparency & trust draw.io + MCP +19

draw.io + MCP 81

Apache 2.0 (30). The privacy policy, v2.3.1 of 18 October 2026, says diagrams are processed and not kept, sets retention for logs (30 days) and user counts (24 months), and lists where data goes. A separate policy for the hosted MCP server (v1.1, 13 October 2026) says diagrams and requests aren't stored or logged, gives retention per item and names Cloudflare and Google Cloud as sub-processors. The two agree, and the 2023 policy's UK-only statement is gone. Neither policy publishes a DPA or says one is available, so the line sits with pen-dev (24) and pushary (25), whose retention tables and sub-processor lists come with a DPA on request (24, 15 on 1 October). No deprecation policy found, though the core ChangeLog records changes such as the Dropbox removal in 32.5.1 (3). Providers and data locations are listed in both policies, with Cloudflare processing in the data centre nearest the caller, which may be outside the UK. We found no telemetry in the MCP tool definitions (18, 10 on 1 October). 30 + 24 + 3 + 18 = 75.

Lucid API + MCP 62

Closed service with published terms (15). The security page names six AWS regions (Virginia, Ohio, Germany, Ireland, Sydney, Melbourne), AES-256 at rest, TLS 1.2 or 1.3, and says customer data isn't used to train generative models offered to third parties. Retention sits in the privacy policy and DPA, which we didn't read (22). The scope docs mark document.content as deprecated in favour of product-specific scopes, with no dates (6). A public subprocessor list is referenced and data regions are named (18).

Schema & documentation draw.io + MCP +14

draw.io + MCP 87

Both servers declare typed input schemas, JSON Schema in the npm tool server and zod in the hosted App (25). www.drawio.com/llms.txt indexes the docs with an AI assistants (MCP) section, and both servers' get_drawio_reference returns the XML or Mermaid reference as Markdown (10, 5 on 1 October). Descriptions say when to use and when not to. create_diagram tells the model to call get_drawio_reference once per format before the first diagram and search_shapes first for industry icons, and the npm open_drawio_xml says to prefer Mermaid outside stencil-based diagrams (20). Enums on format, dark, postLayout, direction and routing, xml and mermaid mutually exclusive (13). Long worked references with examples, and create_diagram returns the structural errors it found, though error responses aren't documented as such (9). Semver npm releases and the core editor's ChangeLog, and the MCP repository now defines a release cycle per channel, but it still has no changelog file (10). 25 + 10 + 20 + 13 + 9 + 10 = 87.

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

Score by category

CategoryWeightdraw.io + MCPLucid API + MCPEdge
Reliability16%4580Lucid API + MCP +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8773draw.io + MCP +14
Agent ergonomics13%5962Lucid API + MCP +3
Security & auth14%5580Lucid API + MCP +25
Payments & pricing10%9038draw.io + MCP +52
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8633draw.io + MCP +53
Transparency & trust7%8162draw.io + MCP +19
Negative events≤1500
TotalB 68.2/100B 65/100

Facts side by side

Factdraw.io + MCPLucid API + MCP
KindMCP serverHTTP API
Vendordraw.ioLucid Software
Hosted endpointhttps://mcp.draw.io/mcphttps://api.lucid.co
TransportsStreamable HTTP, stdioHTTP, Streamable HTTP
AuthNoneOAuth or key
PricingFreeFreemium
x402nono
LicenceApache-2.0proprietary
Tools exposed39
Read-only variant documentednono
llms.txtyesyes
MCP registryio.draw/mcpapp.lucid.mcp/lucid
Last release2026-10-312026-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
Popularity8.5k stars, 25k npm/wknone
Agent reviews4/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate draw.io + MCP higher.

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

draw.io + MCP

Free, keyless and Apache 2.0. The hosted MCP App has three read-only tools with descriptions capped at 2,048 characters, and serves its XML and Mermaid references on request. A privacy policy for the MCP server says diagrams aren't stored. No rate limits, SLA or status monitor cover mcp.draw.io, and the npm server's eight tools carry no annotations.

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

draw.io + MCP

  1. Call get_drawio_reference once per format before the first diagram, then pass mermaid to create_diagram for any type on its Mermaid list. Use xml for icons, mockups or hand-placed layouts
  2. Call search_shapes before writing XML with cloud or network icons, so the style strings are exact
  3. Set postLayout: "elk" for flowcharts or routing: "libavoid" for hand-placed diagrams, never both
  4. Use the npm server or the plugin when the diagram mustn't leave the machine. The hosted App sends it to draw.io's server, which doesn't store it
  5. Expect each reference to cost thousands of tokens when fetched. Fetch only the format you will use

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, draw.io + MCP or Lucid API + MCP?

draw.io + MCP scores 68.2 (B) on agent readiness against Lucid API + MCP's 65 (B), and leads in 4 of 7 scored categories. Lucid API + MCP leads on reliability and security & auth.

Do draw.io + MCP and Lucid API + MCP need an API key?

draw.io + MCP needs no key. Lucid API + MCP takes an API key or an OAuth sign-in.

Can an agent call draw.io + MCP and Lucid API + MCP without installing anything?

Yes. draw.io + MCP has a hosted endpoint at https://mcp.draw.io/mcp and Lucid API + MCP at https://api.lucid.co.

Are draw.io + MCP and Lucid API + MCP open source?

draw.io + MCP is open source (Apache-2.0). No open-source release is listed for Lucid API + MCP.

Other comparisons with draw.io + 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.