MCP Server | Usage in AI Agents

Claude

Updated on October 26, 2026

Connect the Crisp MCP Server to Claude to access your Crisp workspace through supported MCP tools.

This guide covers connector setup, authentication, and a first test in Claude. For token generation and general server configuration, see the MCP Server Quickstart.

Prerequisites

Before you begin, make sure you have:

Access to Claude.
A Crisp workspace and a valid MCP Server authentication token.
The permissions required for the Crisp data and operations you want to access.

If you do not have a token yet, follow the authentication instructions in the Quickstart.

Connect Crisp to Claude

Open Claude and select Customize from the navigation.

Open Connectors.

Click Add to create a connector.

Select the option to add a custom connector.

Enter Crisp as the connector name and configure the MCP Server URL and authentication.

The Crisp MCP Server endpoint is:

https://api.crisp.chat/mcp/

If Claude lets you set a custom request header, use this endpoint with:

Authorization: Bearer <CRISP_MCP_SERVER_TOKEN>

If you cannot configure an Authorization header, use the token in the URL instead:

https://api.crisp.chat/mcp/?token=<URL_ENCODED_CRISP_MCP_SERVER_TOKEN>

URL-encode the token before adding it to the URL. The token-in-URL method is the one shown in the screenshot below, but the Authorization header is preferable when supported.

Step 5: Enter the Crisp MCP Server URL and authentication token

Save the connector, then make sure it is enabled for the conversation in which you want to use Crisp tools.

Keep your token private. Anyone with access to a valid token may be able to use the permissions associated with it.

Verify the connection

Open a conversation in Claude and ask:

Hey, can you pull my latest Crisp conversations?

Claude should request access to the relevant Crisp tool and, once approved, retrieve conversations from your workspace.

Test 1: Asking Claude for the latest Crisp conversations

You can also test with a simple workspace-information request:

Get the information about my Crisp workspace.

This should use the get_website_information tool. If the request fails, check the connector configuration and your token permissions.

Use Crisp tools

Once the connector is working, you can ask Claude to use supported Crisp operations, for example:

Conversations: "Find my latest Crisp conversations."
CRM: "Search my Crisp contacts for this email address."
Knowledge Base: "Retrieve the content of this Knowledge Base article."
Internal notes: "Add an internal note to this conversation."

Some tools modify data or send messages. Check the target workspace and the action before approving a write operation.

See Available Tools for the complete list of operations.

Troubleshooting

Claude cannot connect to the MCP Server

Confirm the endpoint is https://api.crisp.chat/mcp/.
Check that your MCP Server token is valid.
If you use the URL method, confirm that the token is URL-encoded and included in the token query parameter.
If you use a request header, check that it is named Authorization and starts with Bearer .

Crisp tools do not appear in Claude

Check that the custom connector is saved and enabled for the conversation. If the connector is available but a tool is missing, check the Available Tools reference.

A tool returns a permission error

Crisp MCP Server access follows the permissions associated with the authentication token. Make sure your token permits the requested action. See the MCP Server Quickstart for authentication details.