Lucid MCP
Lucid MCP lets agents search, retrieve, summarize, share, export, and create authorized Lucid documents, diagrams, mind maps, sequence diagrams, and org charts.
Verdict
Common use cases
- Pull architecture diagrams into technical discussions
- Summarize whiteboard sessions after design sprints
- Reference flowcharts during process reviews
- Query org charts for team structure questions
- Retrieve mind maps from brainstorming workshops
Integration
- Vendor
- Lucid MCP
- Category
- other
- Auth
- OAUTH2
- Composio slug
lucid_mcp
Tools
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Search for Lucid MCP and click Connect. 3. You'll be redirected to Lucid's OAuth consent screen — sign in with your Lucid account. 4. Grant permissions to read documents, boards, and folder structures (Lucid will list the exact scopes). 5. After authorization, you'll return to Switchy with a green Connected badge. 6. Open any Project and type '@Lucid' in a message to confirm the connection — ask it to list your recent documents or retrieve a specific board by name. 7. If the MCP responds with document titles or metadata, setup is complete.
What teammates see: by default, memories from Lucid MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Recent Diagrams
@Lucid show me the five most recently updated documents in our workspace
Fetch Specific Board
@Lucid retrieve the board titled 'Q1 Product Roadmap' and summarize its main sections
Summarize Whiteboard Session
@Lucid summarize the sticky notes and ideas from the board 'User Research Synthesis Workshop'
Find Architecture Diagram
@Lucid find the Lucidchart document with 'microservices architecture' in the title and describe its components
Check Folder Contents
@Lucid list all documents in the folder named 'Product Design Specs' and show their last modified dates
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@lucid show me all diagrams in the 'Q1 Planning' folder that were updated in the last week
Found 4 diagrams in 'Q1 Planning' modified in the past 7 days: 1. **System Architecture v3** (Lucidchart) — last edited 2 days ago by Sarah Chen 2. **User Flow - Onboarding** (Lucidchart) — last edited 3 days ago by Mike Torres 3. **Database Schema** (Lucidchart) — last edited 5 days ago by you 4. **Sprint 12 Retrospective** (Lucidspark) — last edited 6 days ago by the team Each diagram is accessible via its share link. This list reflects your current folder permissions.
This example shows cross-product search (Lucidchart and Lucidspark). The MCP requires OAuth scope to read your Lucid account's folder structure. Results depend on your organization's sharing settings — diagrams you can't access won't appear.
@lucid create a new flowchart called 'Payment Processing Flow' and add it to the Engineering shared folder
Created **Payment Processing Flow** in the Engineering folder. The diagram is initialized with a blank canvas and set to your organization's default template. Share link: lucid.app/documents/view/abc123 You can now add shapes, connectors, and annotations directly in Lucid, or ask me to help draft content for specific process steps.
Demonstrates document creation with folder placement. The MCP needs write permissions to the target folder. The new diagram inherits your org's default styling and permissions. You'll still work in Lucid's editor for visual layout — the MCP handles metadata and organization.
@lucid review the 'API Integration' diagram and summarize which services connect to the payment gateway
In the **API Integration** diagram, three services connect to the payment gateway: 1. **Checkout Service** — sends transaction requests via REST API 2. **Subscription Manager** — handles recurring billing through webhook events 3. **Refund Processor** — initiates refund calls and logs responses The diagram shows the payment gateway as a central node with bidirectional arrows to these services. Two other services (Inventory and Notifications) connect to downstream systems but not directly to the gateway.
This synthesis example pairs diagram data with AI reasoning to extract architectural insights. The MCP must parse shape labels and connector relationships — accuracy depends on how consistently your team names elements. Complex diagrams with hundreds of shapes may hit response size limits.
Use-case deep-dives
When Lucid MCP fits distributed team documentation workflows
A 6-person engineering team onboarding two contractors needs to turn whiteboard sessions into written runbooks. Lucid MCP connects Switchy to Lucid's diagramming platform via OAuth2, letting the team pull flowcharts and architecture diagrams directly into prompts without screenshot uploads. The win: AI can reference the actual diagram structure (boxes, connectors, labels) instead of guessing from images. This works when your team already lives in Lucid and diagrams change weekly—onboarding docs stay current because the source of truth is live. The threshold: if your diagrams are static PDFs or you diagram once per quarter, the OAuth setup overhead isn't worth it. For teams running daily standups around evolving system maps, Lucid MCP turns visual artifacts into prompt context that actually updates.
Using Lucid MCP to close the loop on retro action items
A 4-person product team runs biweekly retros in Lucid, mapping themes on a shared board. Without the MCP, action items live in screenshots or manual notes—disconnected from the original context. Lucid MCP lets Switchy read the retro board structure directly, so prompts like 'summarize last three retros and flag recurring blockers' can parse the actual sticky-note groupings and vote counts. The payoff is speed: no one transcribes the board, and follow-up prompts can drill into specific clusters. This breaks down if your retros happen in Miro, FigJam, or a Google Doc—Lucid MCP only talks to Lucid. For teams already paying for Lucid and running structured retros there, the MCP turns visual synthesis into queryable history.
When Lucid MCP helps support teams navigate complex user flows
A 3-person support team at a B2B SaaS company maintains customer journey maps in Lucid, tracking where users drop off or file tickets. Lucid MCP connects those maps to Switchy, so support reps can ask 'which step in the onboarding flow generates the most confusion' and get answers grounded in the actual diagram annotations. The advantage: journey maps stay the source of truth instead of becoming stale PDFs. This works when your maps are living documents updated weekly and your team references them during ticket triage. If your journey maps are quarterly deliverables or owned by a separate UX team that doesn't use Switchy, the integration adds friction without payoff. For support teams that diagram workflows and need to query them in real time, Lucid MCP closes the gap between visual strategy and daily execution.
Frequently asked
What does Lucid MCP do in Switchy?
Lucid MCP connects your Lucid workspace (Lucidchart, Lucidspark) to Switchy's AI agents so they can read diagram data, retrieve board content, and understand your visual documentation. Your team can ask questions about flowcharts, org charts, or brainstorm boards without leaving the AI chat interface. The integration uses OAuth2, so you authorise once and Switchy handles token refresh automatically.
Do I need admin access to connect Lucid MCP?
You need a Lucid account with access to the documents you want Switchy to read. Admin rights aren't required unless your workspace has restricted API access at the organisation level. During OAuth2 setup, Lucid will show you exactly which permissions Switchy requests — typically read access to documents and folders you own or have been shared with you.
Can Lucid MCP create or edit diagrams?
Not yet. The current integration focuses on reading diagram content — extracting shapes, text, connections, and metadata so AI agents can answer questions about your visual docs. If you need to create or modify diagrams, you'll still open Lucidchart or Lucidspark directly. We're evaluating write capabilities based on team demand.
How is this different from just opening Lucid in a browser tab?
Opening Lucid directly works fine for visual editing, but Switchy lets your AI agents parse diagram structure and answer questions across multiple documents at once. Instead of manually searching five flowcharts for a specific process step, you ask Switchy and it scans all connected diagrams in seconds. The trade-off is you can't draw or rearrange shapes through the MCP.
Who on the team should connect Lucid MCP?
Anyone who owns or has edit access to the Lucid documents your team references frequently. Each Switchy user connects their own Lucid account, so the integration only sees documents that person can already access. If your team shares a central Lucid workspace, have the owner or a collaborator with broad access connect it first.