Lucid MCP connector
The Lucid connector brings your Lucidchart and Lucidspark documents to Claude, ChatGPT, Cursor and the Elaichi Agent, so you can search, summarize, create, edit, share and export diagrams as PNG from a chat, inside your own Lucid access.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Lucid to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Lucid once
-
Open Connections, choose Add connection, and pick Lucid.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Lucid. Lucid's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Lucid MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Lucid MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Lucid MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Lucid to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Lucid through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Product
Summarize a user flow before the review
Ask for the checkout flow diagram and get the steps, branches and open questions written out, so the review starts with everyone on the same page.
-
Engineering
Turn an architecture note into a diagram
Paste the description of a new service and have a first system diagram created in Lucid, ready to tidy up with the team.
-
IT
Keep the network diagram current after a change
After a switch is replaced or a subnet moves, edit the diagram from a chat instead of hunting for the right shape.
-
HR
Update the org chart when the team changes
Add the new hire, move the reporting line and share the chart with the department lead in one request.
-
Operations
Export a process map for the handbook
Find the latest approval process map and export it as PNG for the handbook or a slide, without opening Lucid.
-
Project management
Share the project plan with stakeholders
Locate the timeline diagram, check what changed this week and share it with the people who need to see it.
Try asking
- “Summarize the checkout flow diagram and list the decision points.”
- “Create a diagram of our new hire onboarding process.”
- “Export the Q3 architecture diagram as PNG for the board deck.”
Compare
Elaichi vs Zapier MCP vs Composio for Lucid
All three can connect Lucid to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Lucid tools | Allow or restrict single Lucid tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Lucid call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
See it in Elaichi
What connecting Lucid gets you
5 screens from the product, each doing one job for your Lucid account.
The agent
Ask about any Lucid diagram in plain words.
Find the right document, summarize it, or draft a new diagram from a chat.
- documents
- diagrams
- boards
- folders
Ask Elaichi to work across your apps.
Summarize the checkout flow diagram and list the decision points.
Create a diagram of our new hire onboarding process.
Export the Q3 architecture diagram as PNG for the board deck.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Lucid works in Claude, ChatGPT and Cursor.
One governed endpoint, signed in over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own Lucid toolbox.
Product maps flows, IT keeps network diagrams, HR works org charts, each in its own scope.
- Product
- Engineering
- IT
- HR
ElaichiToolboxesShared connections
Share one Lucid connection, never a password.
One person connects Lucid, teammates work through it, and nobody else sees a credential.
- Product
- Engineering
- IT infrastructure
- People team
ElaichiConnectionsAudit log
Every change to a Lucid diagram, on record.
When it happened, who did it, what changed and which document, in one log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts the weekly Lucid digest.
New diagrams are fetched, grouped by team, summarized, approved by a person, then posted back.
Lucid digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch documents
Lucid
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Lucid
Queued
Collections and dashboards
Lucid health, computed on a schedule, no model.
Documents created over 14 days, four live metrics and a breakdown by team, refreshed automatically.
Lucid health
Refreshed 4 minutes ago · every 15 minutes · from the documents collection
Documents
1,284 ↓ 12%
Diagrams
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Documents created
Last 14 days
By team
Share of activity
Product 34%
Engineering 27%
IT infrastructure 21%
People team 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Lucid to Claude?
Connect Lucid in Elaichi first: a Lucid sign-in window opens, you sign in as yourself and approve access, and there is no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude can then work with your Lucid documents and diagrams.
Does Lucid work with ChatGPT and Cursor as well as Claude?
Yes. Lucid is connected once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, is used by Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. There is nothing to set up again per client.
What can an AI agent actually do with my Lucid documents?
It can search your Lucid documents, summarize a diagram in plain words, create a new diagram from a description, edit an existing one, share it with a colleague and export it as PNG. Short, concrete asks such as "summarize the onboarding flow" work better than long sentences.
Does connecting Lucid give the AI access to every document in my workspace?
No. The AI only sees the Lucid documents the person who signed in can already see, because every call runs under that person's own Lucid access. Elaichi can narrow that further with restrictions, and it can never widen it.
Can I stop an agent from deleting or changing things in Lucid?
Yes. Restrictions in Elaichi apply per action, so you can allow reading and summarizing Lucid diagrams while blocking edits, sharing or exports. A restricted action is never advertised to the AI client at all, so no prompt can reach it.
What happens to a Lucid connection when someone leaves?
Offboarding the person in Elaichi ends their access to Lucid through every client at once. A shared Lucid connection keeps working for everyone else on the team. Disconnecting Lucid once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Lucid MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Lucid is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Lucid?
Yes. Both let Claude, ChatGPT or Cursor use Lucid. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Lucid call.
How is Elaichi different from Composio for Lucid?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Lucid: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Lucid in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.