Skip to content

Lucid MCP connector

The Lucid connector brings your Lucidchart and Lucidspark documents to Claude, ChatGPT, Cursor, Microsoft Copilot 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.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Summarize the checkout flow diagram and list the decision points.

Working in Lucid with Elaichi

  • Looked in Lucid
Ask anything…
Governance / Audit log Last 24 hours
Lucid Looked in Lucid Emily Carter · Claude · 9:41 AM Done
Lucid Looked in Lucid Megan Brooks · ChatGPT · 9:38 AM Done
Lucid Looked in Lucid Ryan Hayes · Cursor · 9:35 AM Done

How to connect Lucid to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Lucid MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Lucid MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Lucid MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Lucid MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Lucid to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

What teams do with Lucid through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Lucid is logged.

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

What connecting Lucid gets you

5 screens from Elaichi, each doing one job for your Lucid account.

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask about any Lucid diagram in plain words.

Find the right document, summarize it, or draft a new diagram from a chat.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Lucid works in Claude, ChatGPT, Cursor and Microsoft Copilot.

One governed endpoint, signed in over OAuth, no SDK and no shared API key.

ElaichiToolboxes
Name Source template Tools Created

Product toolbox

Lucid · user flows and process maps

Lucid starter 18 Mar 4, 2026

Engineering toolbox

Lucid · architecture and system diagrams

— 9 Mar 2, 2026

IT toolbox

Lucid · network and infrastructure diagrams

— 24 Feb 27, 2026

HR toolbox

Lucid · org charts and team structures

Lucid starter 6 Feb 19, 2026

Operations toolbox

Lucid · process maps and workflows

— 31 Jan 30, 2026

Marketing toolbox

Lucid · journey maps and campaign boards

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Lucid toolbox.

Product maps flows, IT keeps network diagrams, HR works org charts, each in its own scope.

ElaichiConnections
Connection Scope Status Access
LU

Lucid (Product)

Connected by Emily Carter

Personal • Active 1 team · 6 members
LU

Lucid (Engineering)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
LU

Lucid (IT infrastructure)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
LU

Lucid (People team)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
LU

Lucid (Operations)

Connected by Ryan Hayes

Personal • Active Not shared
LU

Lucid (Marketing)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share one Lucid connection, never a password.

One person connects Lucid, teammates work through it, and nobody else sees a credential.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Lucid Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Lucid Documents Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Lucid Documents List Toolbox

Audit log

Every change to a Lucid diagram, on record.

When it happened, who did it, what changed and which document, in one log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Lucid digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch documents

    Lucid

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Lucid

    Queued

Workflows

A schedule drafts the weekly Lucid digest.

New diagrams are fetched, grouped by team, summarized, approved by a person, then posted back.

Lucid health

Refreshed 4 minutes ago · every 15 minutes · from the documents collection

Live

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%

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.

Why connect Lucid's MCP server through Elaichi

Lucid builds and runs this MCP server. Elaichi sits in front of it, so Lucid's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Lucid's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Lucid's tools at the same Elaichi address as every other connected app. Nobody adds Lucid's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Lucid sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Lucid's server. By default, a tool Lucid does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Lucid

    Lucid builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Lucid team.

    help.lucid.co/hc/en-us/articles/360049229652-Get-Lucid-support

Why run a vendor's MCP server through Elaichi →

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Lucid, by what to check
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 Free for one person; $15 per user per month on Gold. 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.

Questions, answered

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, Microsoft Copilot, 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 restricting edits, sharing or exports. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.

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, Microsoft Copilot 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot