Skip to content

Crisp MCP connector

The Crisp connector brings your Crisp conversations, messages, and website inboxes into Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, so your team can read, reply, route, and update chats from any of them, inside each person's own Crisp access.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Summarize unread Crisp conversations from the last 24 hours.

Working in Crisp with Elaichi

  • List all Crisp website
  • Get single Crisp website by ID
  • List all Crisp conversations
Ask anything…
Governance / Audit log Last 24 hours
Crisp List all Crisp conversations Emily Carter · Claude · 9:41 AM Done
Crisp Get single Crisp website by ID Emily Carter · Claude · 9:41 AM Done
Crisp List all Crisp website Emily Carter · Claude · 9:41 AM Done
Crisp Create a Crisp website Megan Brooks · ChatGPT · 9:38 AM Done
Crisp Get single Crisp conversation by ID Ryan Hayes · Cursor · 9:35 AM Done

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

Step by step, for each AI app

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

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

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

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

Crisp 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 Crisp 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 Crisp through Elaichi

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

  • Support

    Catch up on a chat before replying

    Pull the full message history of a Crisp conversation and get a short summary of what the customer asked and what has already been said, before you type a reply.

  • Support

    Reply to customers without switching tabs

    Draft a reply in plain language and send it into the Crisp conversation, then mark the chat read or resolved once the customer is sorted.

  • Support leadership

    Route conversations to the right agent

    Find conversations waiting in the wrong place, assign them to the agent or inbox that should handle them, and reopen any chat that was closed too early.

  • Sales

    Start a conversation with a new lead

    Open a fresh Crisp conversation with a visitor or prospect and send the first message, so the follow-up begins while the lead is still warm.

  • Customer success

    Keep customer details current on the chat

    Update the details attached to a Crisp conversation, such as the contact's email, name, or segments, so the next agent sees the right context.

  • Operations

    Set up a new site inbox in minutes

    Create a Crisp website for a new brand or product site, check its settings, and remove old ones that are no longer in use.

Try asking

  • “Summarize unread Crisp conversations from the last 24 hours.”
  • “Which website has the most open Crisp conversations?”
  • “Compose a reply on the oldest unresolved conversation.”

See all 218 Crisp tools →

What connecting Crisp gets you

6 screens from Elaichi, each doing one job for your Crisp account.

Elaichi Agent

Ask Elaichi to work across your apps.

Summarize unread Crisp conversations from the last 24 hours.

Which website has the most open Crisp conversations?

Compose a reply on the oldest unresolved conversation.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about Crisp conversations, get answers.

Plain language questions run against live Crisp conversations, websites and operators.

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

Claude, ChatGPT, Cursor and Microsoft Copilot reach Crisp.

One org-wide MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiTools
Tool Action Description
List all Crisp website List Get a Crisp website by id. Required: website_id.
Create a Crisp website Create Create a new website in Crisp. Requires name and domain.
Get single Crisp website by ID Get Get a Crisp website by id. Required: id.
Delete a Crisp website by ID Delete Delete a Crisp website by website_id. Required: website_id.
List all Crisp conversations List List Crisp conversations for a website with optional search and filter parameters. Requires website_id and page_number.

Tool catalog

218 Crisp tools ready to call.

Conversations, websites, messages and verification methods listed, with no custom code written.

ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Crisp · conversations and unread queues

Crisp starter 18 Mar 4, 2026

Sales toolbox

Crisp · inbound chats and leads

— 9 Mar 2, 2026

Success toolbox

Crisp · account conversations and follow ups

— 24 Feb 27, 2026

Marketing toolbox

Crisp · websites and chat campaigns

Crisp starter 6 Feb 19, 2026

Engineering toolbox

Crisp · escalated bug conversations

— 31 Jan 30, 2026

Operations toolbox

Crisp · websites, operators and settings

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Crisp toolbox.

Support, sales and ops each see a curated set of Crisp tools.

ElaichiConnections
Connection Scope Status Access
CR

Crisp (Support EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
CR

Crisp (Support US)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
CR

Crisp (Sales)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
CR

Crisp (Success)

Connected by Tyler Reed

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

Crisp (Marketing site)

Connected by Ryan Hayes

Personal • Active Not shared
CR

Crisp (Escalations)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates use Crisp without a credential.

See who connected each Crisp account and how many teams and members share it.

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]

Crisp Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Crisp Conversations Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Crisp Conversations List Toolbox

Audit log

Every Crisp call is on the record.

When, who, what happened, type and resource, appended for each Crisp action.

From answering questions to doing the work

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

Crisp digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch conversations

    Crisp

    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

    Crisp

    Queued

Automations

A schedule drafts your Crisp digest.

Fetch conversations, group them, draft a digest, approve it, post back to Crisp.

Crisp health

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

Live

Conversations

1,284 ↓ 12%

Websites

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Conversations created

Last 14 days

By team

Share of activity

Support EMEA 34%

Support US 27%

Sales 21%

Success 18%

Collections and dashboards

Crisp health, counted not guessed.

Four metrics, 14 days of conversations created, split by team, refreshed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Crisp

All three can connect Crisp 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 Crisp, 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 Crisp tools Allow or restrict single Crisp 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 Crisp 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.

Crisp tools for your AI agents

218 tools are ready to call through Elaichi's MCP endpoint the moment you connect Crisp, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

How do I connect Crisp to Claude?

Two steps. In Elaichi, add the Crisp connector and paste in the API key from your Crisp settings, then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. There is no OAuth application to register in Crisp and no client ID or secret to generate. Once Claude asks you to sign in to Elaichi, your Crisp conversations are available.

Does Crisp work with ChatGPT and Cursor as well as Claude?

Yes. Crisp is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. Each client signs in over OAuth and works with the same Crisp connection.

What can an AI agent actually do with my Crisp data?

It can read a Crisp conversation and its messages, summarize what a customer needs, and send a reply into the chat. It can start a new conversation, mark chats read or unread, reopen or resolve them, move them to another inbox or agent, and update the contact details attached to a conversation. It can also list, create, or remove the websites in your Crisp account. Because Crisp offers a long list of actions, short concrete asks such as "summarize the last conversation from Ana" work better than long paragraphs.

Does connecting Crisp give the AI access to every inbox and website?

No. Every call runs as the person who signed in, so the AI sees only the Crisp websites, inboxes, and conversations that person can already open in Crisp. Elaichi can narrow that access further with restrictions, and it can never widen it beyond what Crisp itself allows that person.

Can my team share one Crisp connection?

Yes. One person connects Crisp with the API key and shares the connection with a team in Elaichi, and nobody else on the team ever handles the key. Each teammate still signs in to Elaichi as themselves, so every reply, routing change, or new conversation in Crisp is logged under their own name.

Can I stop an agent from deleting or changing things in Crisp?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Crisp conversations and sending messages while restricting deleting conversations or removing websites. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

What happens to a Crisp connection when someone leaves?

Offboarding that person in Elaichi ends their access to Crisp through every client at once, with no separate step in Claude, ChatGPT, Cursor, Microsoft Copilot, or Microsoft Copilot. If they were using a shared Crisp connection, it keeps working for everyone else on the team. Disconnecting Crisp once in Elaichi removes it from every client for everyone.

Does the Crisp MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Crisp 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 Crisp?

Yes. Both let Claude, ChatGPT or Cursor use Crisp. 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 Crisp call.

How is Elaichi different from Composio for Crisp?

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 Crisp: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Crisp 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