Head to head · Diagram creation · October 2026 research run
Lucid API + MCP vs Structurizr + MCP
Lucid API + MCP and Structurizr + MCP score within a point of each other on agent readiness, 65 (B) and 64.1 (B). Structurizr + MCP leads on payments & pricing, maintenance & community and transparency & trust. 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 70
- Schema & documentation, 73 against 61
- Agent ergonomics, 62 against 55
- Security & auth, 80 against 43
Watch for
No public changelog for the API or the MCP server
Best for Teams that model architecture in C4 and want an agent to write and check the model as text.
Ahead on
- Payments & pricing, 75 against 38
- Maintenance & community, 88 against 33
- Transparency & trust, 76 against 62
Also in its favour
- Open source
Watch for
The hosted cloud API is gone. Storage and rendering need your own 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 Structurizr + MCP +55
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.
Structurizr + MCP 88
Application release 2026.10.26 and library v6.2.4 on 26 October 2026, 9 days before this check (30). Four releases since 6 August (library v6.2.3 on 17 September, application 2026.09.19, application 2026.10.26 and library v6.2.4), each fixing a named issue (20). Issues are referenced and fixed in the changelogs, but all 200 commits since February are by one person (15). Not in the official MCP registry (a search for structurizr returns none), and the official Java library is current at v6.2.4 (15). CI on every push and Docker base images bumped on 26 October (8). 30+20+15+15+8 = 88.
Security & auth Lucid API + MCP +37
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).
Structurizr + MCP 43
A per-workspace API key in the X-Authorization header, an admin key for listing, and a regenerate endpoint added in May 2026. The MCP server tools take the API key as a tool argument, so the secret passes through the model's context, and server authentication can be switched off entirely (20). Tool groups are enabled one by one, so an agent can be given read without update or delete. There is no read-only key (12). The hosted tools return parse results of the agent's own DSL. Workspaces fetched from a server can hold text written by others (9). No audit log found (0). No security.txt, disclosure policy or bug bounty found, support is the GitHub issue tracker (2).
Payments & pricing Structurizr + MCP +37
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.
Structurizr + MCP 75
Apache 2.0 code with a paid option, the licence for prebuilt binaries. No payment protocol (0). The licence table is public, £300 to £2,400 a month by unique users billed annually, bought by email and paid by bank transfer or PayPal invoice (10). Building from source is free, and a 14-day trial licence comes from trial.structurizr.com with no payment (20). The hosted MCP needs no key and the local tools need no signup (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.
Transparency & trust Structurizr + MCP +14
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).
Structurizr + MCP 76
Apache 2.0, and the prebuilt binaries add a EULA (28). The privacy policy, updated 1 February 2026, covers only licence purchase data, keeps it for ten years after the licence ends, and says Structurizr has no access to data in your installation. The hosted MCP isn't covered (20). The end-of-life page and cloud migration guide gave dated notice, sign-ups closed 31 December 2025 and shutdown on 30 September 2026; the page was taken down on 25 October after the shutdown and stays readable in the docs repository's history (20). No telemetry mentioned in the docs or EULA, and a search of the source found no analytics or usage calls (12).
Schema & documentation Lucid API + MCP +12
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).
Structurizr + MCP 61
OpenAPI 3.0 definition for the workspace JSON and API, and the MCP tools get typed schemas from their Java signatures (25). No llms.txt found (0). Tool descriptions are one line, such as "Validates a Structurizr DSL workspace", with the parameter described as "DSL" (6). Required flags and a numeric workspace ID, no enums (8). curl examples for each API case, errors undocumented, and tools return the raw exception message (7). Dated changelogs for the application and the library (15).
Reliability Lucid API + MCP +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.
Structurizr + MCP 70
The hosted cloud API shut down on 30 September 2026, so what an agent calls now is a server you run plus a small hosted MCP, and we used the self-hosted checklist. Prebuilt binaries and Docker images with Java 21 stated (20). A Maven workflow builds and runs the unit tests on every push to main and on pull requests, integration tests excluded, pass state unread because GitHub's pages refuse our reader (15, the value this run gives public CI that runs the tests with an unread result). The changelogs fix reported issues #131, #132, #135 and #137 within weeks of filing, open issues not read (15). Date-stamped application releases and a semver library (v6.2.4), each with a changelog (12). The server is a stable product, but the released MCP module's README still calls it "an experimental MCP server" and mcp.structurizr.com has no status page or published limits (8). 20+15+15+12+8 = 70.
Score by category
| Category | Weight | Lucid API + MCP | Structurizr + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 70 | Lucid API + MCP +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 73 | 61 | Lucid API + MCP +12 |
| Agent ergonomics | 13% | 62 | 55 | Lucid API + MCP +7 |
| Security & auth | 14% | 80 | 43 | Lucid API + MCP +37 |
| Payments & pricing | 10% | 38 | 75 | Structurizr + MCP +37 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 33 | 88 | Structurizr + MCP +55 |
| Transparency & trust | 7% | 62 | 76 | Structurizr + MCP +14 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 65/100 | B 64.1/100 |
Facts side by side
| Fact | Lucid API + MCP | Structurizr + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Lucid Software | Structurizr |
| Hosted endpoint | https://api.lucid.co | https://mcp.structurizr.com/mcp |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | proprietary | Apache-2.0 |
| Tools exposed | 9 | 6 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | app.lucid.mcp/lucid | not listed |
| Last release | 2026-06-15 | 2026-10-26 |
| Terms last updated | couldn't be read | not read yet |
| Privacy policy last updated | couldn't be read | not read yet |
| Customer content may train models | couldn't be read | not read yet |
| Terms restrict automated access | couldn't be read | not read yet |
| Terms restrict benchmarking | couldn't be read | not read yet |
| Terms or service can change without notice | couldn't be read | not read yet |
| Arbitration or class-action waiver | couldn't be read | not read yet |
| Popularity | none | 419 stars |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Lucid API + MCP | Structurizr + MCP |
|---|---|---|
| GullBrowser and end-to-end tester | 3/5 Developer tools are a setting, and an admin can unset them | 3/5 The cloud is gone, so bring a server |
| QuillDocumentation and schema critic | 3/5 Typed REST reference, second-hand MCP tools | 3/5 One-line descriptions and a destructive default |
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.
Structurizr + MCP
One text model generates several C4 architecture views, and the project shipped four releases between 17 September and 26 October 2026. The hosted cloud API has closed, so storage and rendering need a customer-managed server, and the free hosted MCP covers only validation, parsing and 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
Structurizr + MCP
- Call
validateand theninspecton the DSL before pushing a workspace - Use the Mermaid export when the diagram has to render in Markdown without a Structurizr server
- Export needs a view key. Parse the DSL first to list the views
- Run the
structurizr/mcpimage with only the flags you need, such as-dsl -server-read, to keep write and delete tools out of reach - The workspace API returns JSON, never images. PNG and SVG come from the separate export command
Questions
Which is better for AI agents, Lucid API + MCP or Structurizr + MCP?
Lucid API + MCP and Structurizr + MCP score within a point of each other on agent readiness, 65 (B) and 64.1 (B). Structurizr + MCP leads on payments & pricing, maintenance & community and transparency & trust.
Do Lucid API + MCP and Structurizr + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Lucid API + MCP and Structurizr + MCP without installing anything?
Yes. Lucid API + MCP has a hosted endpoint at https://api.lucid.co and Structurizr + MCP at https://mcp.structurizr.com/mcp.
Are Lucid API + MCP and Structurizr + MCP open source?
No open-source release is listed for Lucid API + MCP. Structurizr + MCP is open source (Apache-2.0).
Other comparisons with Lucid API + MCP or Structurizr + MCP
- AI Diagram Maker MCP vs Lucid API + MCP
- AI Diagram Maker MCP vs Structurizr + MCP
- Cloudviz API vs Lucid API + MCP
- Cloudviz API vs Structurizr + MCP
- Diagrams.so API + MCP vs Lucid API + MCP
- Diagrams.so API + MCP vs Structurizr + MCP
- draw.io + MCP vs Lucid API + MCP
- draw.io + MCP vs Structurizr + MCP
- Eraser API + MCP vs Lucid API + MCP
- Eraser API + MCP vs Structurizr + MCP
- ExcaliClaw vs Lucid API + MCP
- ExcaliClaw vs Structurizr + MCP
- Excalidraw vs Lucid API + MCP
- Excalidraw vs Structurizr + MCP
- Lucid API + MCP vs Mermaid Chart MCP
- Lucid API + MCP vs Mumble
- Lucid API + MCP vs Mural MCP
- Lucid API + MCP vs PlantUML
- Lucid API + MCP vs tldraw SDK + MCP
- Lucid API + MCP vs Whimsical MCP
- Mermaid Chart MCP vs Structurizr + MCP
- Mumble vs Structurizr + MCP
- Mural MCP vs Structurizr + MCP
- Structurizr + MCP vs tldraw SDK + MCP
- Structurizr + MCP vs Whimsical MCP
- D2 vs Lucid API + MCP
- D2 vs Structurizr + MCP
- Kroki vs Lucid API + MCP
- Kroki vs Structurizr + MCP
- PlantUML vs Structurizr + MCP
Machine-readable
- This page as Markdown
/compare/lucid-vs-structurizr.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lucid.json·/api/v1/tools/structurizr.json - From a terminal
anchor compare lucid structurizr(the CLI) - Over MCP
compare_tools {"a": "lucid", "b": "structurizr"}at/mcp, no key