# 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.

Source: https://elaichi.ai/connectors/lucid/

## Facts

| | |
| --- | --- |
| Application | Lucid |
| Category | Design |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Lucid builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | help.lucid.co/hc/en-us/articles/360049229652-Get-Lucid-support |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Lucid is connected

- 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.

## Connect Lucid in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Lucid.
2. Optionally set Share with, then press Connect.
3. Approve it in Lucid. Lucid's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Lucid tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Lucid MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Lucid to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Lucid tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Lucid through Elaichi

### Summarize a user flow before the review

Product. 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.

### Turn an architecture note into a diagram

Engineering. Paste the description of a new service and have a first system diagram created in Lucid, ready to tidy up with the team.

### Keep the network diagram current after a change

IT. After a switch is replaced or a subnet moves, edit the diagram from a chat instead of hunting for the right shape.

### Update the org chart when the team changes

HR. Add the new hire, move the reporting line and share the chart with the department lead in one request.

### Export a process map for the handbook

Operations. Find the latest approval process map and export it as PNG for the handbook or a slide, without opening Lucid.

### Share the project plan with stakeholders

Project management. Locate the timeline diagram, check what changed this week and share it with the people who need to see it.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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 my team share one Lucid connection?

Yes. One person connects Lucid in Elaichi and shares the connection with a team, and nobody else handles a password or token. Each teammate still signs in to Elaichi as themselves, so the audit log names who touched which Lucid document.

### 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.