Lucid
Let your coding agent create Lucid diagrams, search boards, share links, and summarize visual docs without leaving the chat.
Overview
Lucid is an MCP server for the Build phase that creates Lucid diagrams, searches and shares boards, and retrieves documents so your agent can summarize visual specs.
What is this MCP server?
- Creates Lucid diagrams from natural-language prompts inside MCP-connected agents
- Searches and retrieves existing Lucid documents for context before you change code
- Shares and summarizes boards so stakeholders get a one-shot narrative
- Streamable HTTP remote at mcp.lucid.app (schema version 0.1.0)
- MCP integration for Claude Code, Cursor, and other MCP clients—not a standalone diagram editor
What problem does it solve?
You waste context switching between the IDE and Lucid when the agent cannot create or query the diagrams your team already treats as canonical.
Who is it for?
Indie builders and tiny teams who document systems in Lucid and want Claude or Cursor to keep those boards in sync with what they are shipping.
Skip if: Teams that do not use Lucid or only need quick one-off sketches with no shared workspace.
What do I get? / Deliverables
After you register the Lucid MCP remote, the agent can generate and reference Lucid artifacts while you stay in one thread for implementation and documentation.
- New or updated Lucid diagrams created via agent prompts
- Retrieved Lucid content and summaries usable in specs or PR descriptions
- Shareable Lucid links produced from agent-driven workflows
Recommended MCP Servers
Journey fit
Diagrams and living documentation sit in the build phase when you are capturing architecture, flows, and handoff artifacts. Docs subphase is where visual specs, system maps, and shareable boards replace scattered screenshots in READMEs and tickets.
How it compares
Lucid MCP is a hosted workspace connector, not an agent skill that draws diagrams locally without Lucid cloud.
Common Questions / FAQ
Who is Lucid MCP for?
Solo and indie builders who rely on Lucid for architecture and process diagrams and want their AI coding agent to read and write those assets through MCP.
When should I use Lucid MCP?
Use it during build and docs work when you need new diagrams, searches across existing boards, or summaries of Lucid content before merging or writing specs.
How do I add Lucid MCP to my agent?
Add the streamable HTTP remote https://mcp.lucid.app/mcp in your MCP client config per Lucid’s connector docs, authenticate with your Lucid account as required, then reload tools in Claude Code or Cursor.