D2 vs Lucid API + MCP

D2

A single local command turns text into a diagram in six formats with no account, key or network call, and CI passes on the default branch. The language is at 0.9.0 with no stable release, its company sponsor has shut down, and one maintainer with limited time wrote every commit since July.

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.

D2

1. Check the exit status of d2, never the output file. The man page says a partial render can be written when an error occurs
2. Run d2 validate file.d2 before rendering, and d2 fmt to normalise the source
3. Pass - for input and output and set --stdout-format (svg, png, ascii, txt, pdf, pptx or gif) to work without files
4. Use --stdout-format ascii when the reader is a text-only model
5. Pass --bundle=false or review image URLs and imports before rendering D2 text from an untrusted source. Release 0.9.0 fetches remote images when bundling

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 60 seconds or back off. Create Mermaid Diagram allows 60 calls a minute
5. Sharing and embed endpoints need an OAuth token. An API key won't work there