Helpdesk
Crisp MCP connector
The Crisp connector brings your Crisp conversations, messages, and website inboxes into Claude, ChatGPT, Cursor, 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.
-
How it connects. Connects with an API key. 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 Crisp to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Crisp once
-
Open Connections, choose Add connection, and pick Crisp.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Crisp API key. One person generates a token in Crisp and pastes it once. Everyone else works through Share with, and never sees it.
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.
Connect Crisp to 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.
Connect Crisp to 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.
Connect Crisp to 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 Crisp 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 Crisp through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
No tools match your search.
See it in Elaichi
What connecting Crisp gets you
6 screens from the product, each doing one job for your Crisp account.
The agent
Ask about Crisp conversations, get answers.
Plain language questions run against live Crisp conversations, websites and operators.
- conversations
- websites
- messages
- operators
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Crisp.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
218 Crisp tools ready to call.
Conversations, websites, messages and verification methods listed, with no custom code written.
- List all Crisp website
- Create a Crisp website
- Get single Crisp website by ID
- Delete a Crisp website by ID
Toolboxes
Every team gets its own Crisp toolbox.
Support, sales and ops each see a curated set of Crisp tools.
- Support
- Sales
- Success
- Marketing
Shared connections
Teammates use Crisp without a credential.
See who connected each Crisp account and how many teams and members share it.
- Support EMEA
- Support US
- Sales
- Success
Audit log
Every Crisp call is on the record.
When, who, what happened, type and resource, appended for each Crisp action.
- When
- Who
- What happened
- Type
Launching 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 your Crisp digest.
Fetch conversations, group them, draft a digest, approve it, post back to Crisp.
Crisp digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch conversations
Crisp
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
Crisp
Queued
Collections and dashboards
Crisp health, counted not guessed.
Four metrics, 14 days of conversations created, split by team, refreshed on schedule.
Crisp health
Refreshed 4 minutes ago · every 15 minutes · from the conversations collection
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 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 blocking deleting conversations or removing websites. A blocked action is never advertised to Claude, ChatGPT, or Cursor at all, so no prompt, however worded, can reach it.
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, or Cursor. 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.
Put Crisp in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.