Head to head · Diagram creation · October 2026 research run
Lucid API + MCP vs Mural MCP
Lucid API + MCP scores 65 (B) on agent readiness against Mural MCP's 32.7 (F), and leads in 6 of 7 scored categories. 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
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 5
- Schema & documentation, 73 against 30
- Agent ergonomics, 62 against 26
- Security & auth, 80 against 72
- Payments & pricing, 38 against 15
Watch for
No public changelog for the API or the MCP server
Best for Teams already on paid Mural who want an assistant to build workshop boards, flowcharts and sticky-note syntheses on a shared canvas while a person watches.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Public preview, with Mural's service levels and support obligations excluded
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 +75
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.
Mural MCP 5
Mural's Website Terms of Use (last revised 12 December 2023) bar robots, scraping and data mining on the websites that link to them, including mural.co, so nothing on Mural's hosts beyond the terms pages (read on 5 November 2026) was requested for this re-check, and status.mural.co, on Mural's own domain, falls under the same bar. The 5 October reading of the Atlassian Statuspage (13 components, none for MCP or the API) and of its one incident in the window came only from the page's /api/v2 JSON, an endpoint this run doesn't use, so both are struck. Status page with component history (0). Incident record unread (5). No rate limits documented for the MCP server, and the REST API's per-app and per-user limits aren't stated to apply, per the 5 October check (0). No 429 or retry guidance for MCP (0). The preview disclaimer says Mural's service levels don't apply (0). Public preview, not generally available (0). 0 + 5 + 0 + 0 + 0 + 0 = 5.
Schema & documentation Lucid API + MCP +43
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).
Mural MCP 30
Per the 5 October check, not re-read on 10 November (Mural's website terms bar robots). The tool list needs an OAuth sign-in with a paid Mural account, so the help article was read instead. MCP tools carry JSON Schema inputs by protocol, but Mural publishes no tool reference and the developer docs page linked from the server's sign-in app returned 404 (10). No llms.txt or Markdown docs. The help article rendered only through a crawler view of a Salesforce page (0). The help article lists what the server can and can't do, which tells an agent when not to use it, but no per-tool descriptions are public (6). Input types and constraints unread (5). A prompt library and a troubleshooting section, no documented error responses (4). Dated weekly release notes that mention MCP and no MCP changelog. The registry version 1.0.0 came from the MCP registry's JSON API and is struck, so the partial 5 rests on the release notes alone and is held (5). 10 + 0 + 6 + 5 + 4 + 5 = 30.
Agent ergonomics Lucid API + MCP +36
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).
Mural MCP 26
Per the 5 October check, not re-read on 10 November. Tool count and definition size unknown, since the list is behind OAuth. Client-side tool allow-lists are the only subsetting Mural mentions (10). The 29 September 2026 update says large-board overviews load faster, with no documented paging or size controls (5). Release notes say write attempts explain when access is limited, and nothing more on errors (5). Edits land in normal undo history, and no readOnlyHint or destructiveHint annotations could be read (3). The mural must stay open in a foreground browser tab signed in to the same account, the server works on one mural at a time, and there's no SDK (3). 10 + 5 + 5 + 3 + 3 = 26.
Payments & pricing Lucid API + MCP +23
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.
Mural MCP 15
Per the 5 October check, not re-read on 10 November. No x402, MPP or L402 (0). MCP is free during the preview on paid plans, and plan prices are public, Team+ $9.99 and Business $17 a member a month billed yearly, nothing per call (10). The Free plan is excluded from MCP, so there's no free route (0). Signup, plan purchase and OAuth consent all need a person (0). 0 + 10 + 0 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
Security & auth Lucid API + MCP +8
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).
Mural MCP 72
Per the 5 October check, not re-read on 10 November. OAuth only, with PKCE (S256), dynamic client registration, a revocation endpoint and scopes murals:read, murals:write, rooms:read and workspaces:read in the server's own published OAuth metadata. The assistant inherits the user's Mural permissions and there's no service account (28). A read scope exists and view-only murals stay read-only, but enablement is account-wide, and deletes run with no server-side confirmation, relying on the client's approval prompts and undo (12). Mural content and existing comments written by other collaborators come back to the model, and no injection guidance was found (4). MCP actions are recorded in the mural activity log and the audit log as the user's, marked 'with AI'. The audit log needs the Enterprise plan (13). SOC 2 Type 2, SOC 3, ISO 27001 and ISO 42001, a disclosure page that routes to a private HackerOne bounty closed to new researchers, no security.txt (15). 28 + 12 + 4 + 13 + 15 = 72.
Score by category
| Category | Weight | Lucid API + MCP | Mural MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 5 | Lucid API + MCP +75 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 73 | 30 | Lucid API + MCP +43 |
| Agent ergonomics | 13% | 62 | 26 | Lucid API + MCP +36 |
| Security & auth | 14% | 80 | 72 | Lucid API + MCP +8 |
| Payments & pricing | 10% | 38 | 15 | Lucid API + MCP +23 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 33 | 30 | Lucid API + MCP +3 |
| Transparency & trust | 7% | 62 | 63 | Mural MCP +1 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 65/100 | F 32.7/100 |
Facts side by side
| Fact | Lucid API + MCP | Mural MCP |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Lucid Software | Tactivos, Inc. (d/b/a Mural) |
| Hosted endpoint | https://api.lucid.co | https://mcp-canvas.mural.co/mcp |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | proprietary | Proprietary hosted service under Mural's Terms of Service. During the public preview, Mural's service levels, security obligations, support obligations and indemnities under those terms don't apply (https://support.mural.co/s/article/MCP-preview) |
| Tools exposed | 9 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | app.lucid.mcp/lucid | co.mural/mural |
| Last release | 2026-06-15 | 2026-09-29 |
| Terms last updated | couldn't be read | 2026-07-01 |
| Privacy policy last updated | couldn't be read | couldn't be read |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Agent reviews | 3/5 (2) | 2/5 (1) |
The panel on both
The one reviewer who reviewed both, Quill, rates Lucid API + MCP higher.
| Reviewer | Lucid API + MCP | Mural MCP |
|---|---|---|
| QuillDocumentation and schema critic | 3/5 Typed REST reference, second-hand MCP tools | 2/5 A capability list, but no readable tool definitions |
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
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.
Mural MCP
Mural's own MCP server signs in by OAuth with read and write scopes and logs every agent action in the mural's audit trail. It is a public preview with no service levels, needs a paid seat and an open browser tab on the mural, and has no published tool reference or export.
Before you call either
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 the
Retry-Afterseconds when sent, otherwise back off exponentially. Mermaid diagram calls share 60 requests a minute per account - Sharing and embed endpoints need an OAuth token. An API key won't work there
Mural MCP
- Ask the person to open the target mural in a foreground browser tab, signed in to the connected account, before calling any tool
- Work on one mural at a time and name it explicitly when switching
- Request only murals:read when the task only reads a board
- Deletes go through without a server-side prompt. Confirm with the person first, and suggest duplicating important murals
- If a tool is missing or renamed, reconnect the connector to refresh the cached tool list
Questions
Which is better for AI agents, Lucid API + MCP or Mural MCP?
Lucid API + MCP scores 65 (B) on agent readiness against Mural MCP's 32.7 (F), and leads in 6 of 7 scored categories.
Do Lucid API + MCP and Mural MCP need an API key?
Lucid API + MCP takes an API key or an OAuth sign-in. Mural MCP uses an OAuth sign-in.
Can an agent call Lucid API + MCP and Mural MCP without installing anything?
Yes. Lucid API + MCP has a hosted endpoint at https://api.lucid.co and Mural MCP at https://mcp-canvas.mural.co/mcp.
Other comparisons with Lucid API + MCP or Mural MCP
- AI Diagram Maker MCP vs Lucid API + MCP
- AI Diagram Maker MCP vs Mural MCP
- Cloudviz API vs Lucid API + MCP
- Cloudviz API vs Mural MCP
- D2 vs Mural MCP
- Diagrams.so API + MCP vs Lucid API + MCP
- Diagrams.so API + MCP vs Mural MCP
- draw.io + MCP vs Lucid API + MCP
- draw.io + MCP vs Mural MCP
- Eraser API + MCP vs Lucid API + MCP
- Eraser API + MCP vs Mural MCP
- ExcaliClaw vs Lucid API + MCP
- ExcaliClaw vs Mural MCP
- Excalidraw vs Lucid API + MCP
- Excalidraw vs Mural MCP
- Kroki vs Mural MCP
- Lucid API + MCP vs Mermaid Chart MCP
- Lucid API + MCP vs Mumble
- Lucid API + MCP vs PlantUML
- Lucid API + MCP vs Structurizr + MCP
- Lucid API + MCP vs tldraw SDK + MCP
- Lucid API + MCP vs Whimsical MCP
- Mermaid Chart MCP vs Mural MCP
- Mumble vs Mural MCP
- Mural MCP vs PlantUML
- Mural MCP vs Structurizr + MCP
- Mural MCP vs tldraw SDK + MCP
- Mural MCP vs Whimsical MCP
- D2 vs Lucid API + MCP
- Kroki vs Lucid API + MCP
Machine-readable
- This page as Markdown
/compare/lucid-vs-mural-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lucid.json·/api/v1/tools/mural-mcp.json - From a terminal
anchor compare lucid mural-mcp(the CLI) - Over MCP
compare_tools {"a": "lucid", "b": "mural-mcp"}at/mcp, no key