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

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

## Facts

| | |
| --- | --- |
| Application | Crisp |
| Category | Helpdesk |
| AI tools | 218 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, 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 Crisp is connected

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

## Connect Crisp in Elaichi

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

1. Open Connections, choose Add connection, and pick Crisp.
2. Optionally set Share with, then press Connect.
3. 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.

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

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

## Crisp MCP connector for Claude Code

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

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. The plugin directory lives at chatgpt.com/plugins.

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

## Crisp MCP connector for Microsoft Copilot

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

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

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

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

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Crisp tool needs "Use your connected apps". 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. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Crisp through Elaichi

### Catch up on a chat before replying

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

### Reply to customers without switching tabs

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

### Route conversations to the right agent

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

### Start a conversation with a new lead

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

### Keep customer details current on the chat

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

### Set up a new site inbox in minutes

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

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

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

## All 218 Crisp tools

Every tool below is callable through https://api.elaichi.ai/mcp once Crisp is connected, subject to the toolbox it is in and the restrictions on the caller.

- **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.
- **Get single Crisp conversation by ID** (Get). Get a single Crisp conversation by session. Returns the conversation object for the given website. Requires website_id and session_id.
- **Create a Crisp conversation** (Create). Create a new conversation in Crisp for the given website. Returns the created conversation reference. Requires website_id.
- **Delete a Crisp conversation by ID** (Delete). Delete a Crisp conversation by session. Requires website_id and session_id.
- **Crisp conversations get verify** (Get). Get the verify status for a Crisp conversation. Requires website_id and session_id.
- **Crisp conversations update verify** (Update). Update the verify status for a Crisp conversation. Requires website_id and session_id.
- **Crisp conversations initiate** (Action). Initiate a Crisp conversation with an existing session. Requires website_id and session_id.
- **Crisp conversations compose** (Action). Update the compose state (typing indicator) on a Crisp conversation. Requires website_id and session_id.
- **Crisp conversations mark read** (Action). Mark messages as read in a Crisp conversation. Requires website_id and session_id.
- **Crisp conversations mark unread** (Action). Mark messages as unread in a Crisp conversation. Requires website_id and session_id.
- **Crisp conversations mark delivered** (Action). Mark messages as delivered in a Crisp conversation. Requires website_id and session_id.
- **Crisp conversations update open** (Update). Update the open state of a Crisp conversation. Requires website_id and session_id.
- **Crisp conversations get routing** (Get). Get the routing assignment of a Crisp conversation. Requires website_id and session_id.
- **Crisp conversations update routing** (Update). Update the routing assignment of a Crisp conversation. Requires website_id and session_id.
- **Crisp conversations update inbox** (Update). Update the inbox a Crisp conversation is categorized under. Requires website_id and session_id.
- **Crisp conversations get metas** (Get). Get metas (subject, segments, nickname, email, etc.) for a Crisp conversation. Requires website_id and session_id.
- **Crisp conversations update metas** (Update). Update metas for a Crisp conversation. Requires website_id and session_id.
- **List all Crisp messages** (List). List messages in a Crisp conversation. Returns message objects including type, from, origin, content, and fingerprint. Required: website_id, session_id.
- **Get single Crisp message by ID** (Get). Get a single message in a Crisp conversation by fingerprint. Returns the message object including type, from, origin, content, and fingerprint. Required: website_id, session_id, fingerprint.
- **Create a Crisp message** (Create). Send a message in a Crisp conversation. Returns the created message details including its fingerprint. Required: website_id, session_id, type, from, origin, content.
- **Update a Crisp message by ID** (Update). Update a message in a Crisp conversation by fingerprint. Required: website_id, session_id, fingerprint, content.
- **Delete a Crisp message by ID** (Delete). Remove a message in a Crisp conversation by fingerprint. Required: website_id, session_id, fingerprint.
- **List all Crisp spam conversations** (List). List spam conversations for a Crisp website. Required: website_id, page_number.
- **Crisp spam conversations get content** (Get). Get the content of a spam conversation in Crisp. Required: website_id, spam_id.
- **Crisp spam conversations submit decision** (Action). Submit a decision on a spam conversation in Crisp (e.g. confirm spam or restore). Required: website_id, spam_id.
- **Create a Crisp inbox** (Create). Create a new inbox for a Crisp website. Requires website_id.
- **Get single Crisp inbox by ID** (Get). Get a Crisp website inbox by id. Requires website_id and inbox_id.
- **Update a Crisp inbox by ID** (Update). Update (save) a Crisp website inbox by id. Requires website_id and inbox_id.
- **Delete a Crisp inbox by ID** (Delete). Delete a Crisp website inbox by id. Requires website_id and inbox_id.
- **List all Crisp conversation pages** (List). List visited pages for a Crisp conversation. Required: website_id, session_id, page_number.
- **List all Crisp conversation events** (List). List events for a Crisp conversation session. Required: website_id, session_id, page_number.
- **List all Crisp conversation files** (List). List files exchanged in a Crisp conversation, paginated. Required: website_id, session_id, page_number.
- **Get single Crisp conversation state by ID** (Get). Get the state of a Crisp conversation. Required: website_id, session_id.
- **Update a Crisp conversation state by ID** (Update). Update the state of a Crisp conversation. Required: website_id, session_id.
- **List all Crisp conversation relations** (List). List relations associated with a Crisp conversation. Required: website_id and session_id.
- **List all Crisp conversation participants** (List). List participants of a Crisp conversation. Required: website_id and session_id.
- **Update a Crisp conversation participant by ID** (Update). Save the list of participants for a Crisp conversation. Required: website_id and session_id.
- **Get single Crisp conversation block by ID** (Get). Get the blocked status of a Crisp conversation. Requires website_id and session_id.
- **Update a Crisp conversation block by ID** (Update). Update the blocked status of a Crisp conversation. Requires website_id and session_id.
- **Get single Crisp message original by ID** (Get). Get the original message content for a Crisp conversation message. Required: website_id, session_id, original_id.
- **Crisp verify identities request** (Verify). Request identity verification for a Crisp conversation. Required: website_id, session_id.
- **Crisp verify identities redeem link** (Verify). Redeem the identity verification link for a Crisp conversation. Required: website_id, session_id.
- **Create a Crisp transcript** (Create). Request an email transcript for a Crisp conversation. Required: website_id, session_id, and a recipient (to or email).
- **Create a Crisp purge** (Create). Request a chatbox binding purge for a Crisp conversation. Required: website_id, session_id.
- **Create a Crisp feedback** (Create). Request user feedback for a Crisp conversation. Required: website_id, session_id.
- **List all Crisp browsings** (List). List browsing sessions for a Crisp conversation. Required: website_id, session_id.
- ...and 168 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
