MCP Server

Quickstart

Updated on May 27, 2026

Crisp runs a MCP server that allows you to access and manipulate data from your Crisp workspace, like a developer would do using the Crisp REST API.

Connecting to the Crisp MCP Server is very easy. If you already used the Crisp REST API, then the process will feel familiar to you.

The Crisp MCP Server is available at: https://api.crisp.chat/mcp/

⏰ 1 Minute Setup

Follow those steps to connect to the Crisp MCP Server in your favorite AI tool:

Add a new MCP server in your tool
Choose transport type: Streamable HTTP
In the URL, enter: https://api.crisp.chat/mcp/
Provide the following Authorization header: Authorization: Bearer <CRISP_MCP_SERVER_TOKEN>
Hit the connect to MCP server button
In the list of tools, you should now see tools like: get_website (more tools will be listed)
To verify your authentication token is valid, make a tool call and check for the response

Alternatively, you can also pass the token as a ?token=<CRISP_MCP_SERVER_TOKEN> URL parameter, if your AI provider does not support the Authorization header. Prefer using the Authorization header if available, as it is much more secure.

When using the URL parameter method, note that the token must always be URL-encoded first. You can use online URL-encoding tools, but also programmatic ways such as JavaScript's encodeURIComponent("<CRISP_MCP_SERVER_TOKEN>") function.

How to connect to the Crisp MCP Server (here, in Le Chat from Mistral)

Authentication

How to obtain my authentication token?

Your MCP Server token can be generated in one click:

Open the Crisp Dashboard;
Go to Settings > Workspace Settings > Advanced configuration;
In the MCP Server Token section, click Generate Token;
Copy your token authorization value (it is only shown once);

🆘 Beware! If you already generated a keypair to access the Crisp REST API in this section, and you did not take note of your MCP Server token, then you will need to re-generate all the tokens altogether. Since your MCP Server token is tied to your REST API token, re-generating one means re-generating everything. If your workspace already has a token, talk to other developers in your team first if you might be breaking something.

Retrieve your MCP Server token in 1 click from Crisp

How to configure my authentication token?

The Crisp MCP Server uses the same token as the Crisp REST API. As such, depending on the type of token you will be using, the same ACLs enforced on the REST API apply (e.g. token scopes).

Authenticate to the MCP Server using this custom header

Your MCP Server token already contains your workspace website_id and holds the tier website. You do not need to specify your workspace identifier when talking to your AI agent.

Usage

What can I do with the MCP Server?

The Crisp MCP Server offers tools to access data from your Crisp workspace, but also make write operations (such as changing a conversation state, sending messages, etc.).

Here are examples of things you can now ask your AI Agent:

1️⃣ "Send a survey to resolved conversations from yesterday, asking if they were satisfied with the support provided."
2️⃣ "Tell me which operators are online in my workspace."
3️⃣ "Suggest improvements to my helpdesk article about our refund policy, users said they were confused about the maximum delay after purchase."