Crisp

What the Crisp MCP server does

Crisp MCP server lets an MCP-compatible client query data from Crisp, a platform for customer support, live chat, CRM, and helpdesk operations. The integration covers the official Crisp REST API v1 at api.crisp.chat and is designed for read-only access.

Supported data areas include conversations and messages, contacts or people, knowledge base articles, categories and languages, campaigns, operators, visitors, and website settings. That makes it suitable for questions such as which conversations are open, which contacts arrived recently, or which articles are published.

The repository is a public wrapper containing manifests, documentation, and agent skills. The hosted MCP endpoint is proprietary, while the repository is released under MIT.

How it works

The Crisp MCP server is accessed through MCP over HTTP. For the hosted deployment, clients connect to:

https://api.mcp.ai/p_crisp

Authentication uses a pair of tokens generated in Crisp under Settings, Workspace settings, and Advanced configuration.

A single exposed entry point, search_tools, provides access to the MCP catalog. Although the server presents one MCP tool, its documented purpose is to query the supported Crisp REST API areas through that entry point. Returned data is sent to the LLM host selected by the user, such as Claude, ChatGPT, Cursor, or a custom agent.

Setup and configuration

The hosted endpoint can be added to Claude Web or Claude Desktop through Claude's custom connector settings. Cursor and VS Code have installation links in the project documentation. Other clients can use the same HTTP URL if they support MCP over HTTP.

No environment variable configuration is documented for the hosted service. To connect Crisp data, configure the required Crisp token pair through the applicable authentication flow rather than relying on a local server configuration described in this listing.

Tools and capabilities

The available MCP tool is:

• search_tools: the single entry point for the MCP catalog.

Through the integration, agents can read:

• Crisp conversations and messages
• Contacts and people
• Knowledge base articles, categories, and languages
• Campaigns
• Operators
• Visitors
• Website configuration

It is therefore intended for inspection, lookup, and question answering rather than sending messages, editing contacts, publishing articles, or changing settings.

Limitations and notes

Access is read-only, so workflows that need to modify Crisp data are outside the stated scope. The hosted MCP service is proprietary even though the public wrapper repository is MIT-licensed.

Crisp data returned by the tools is passed to the LLM host chosen by the user. The project identifies Crisp IM SAS and the selected LLM host as subprocessors and recommends considering plans with training opt-out controls. Review the project's privacy documentation before using the connection with sensitive support or customer data.

The integration is documented for Claude Desktop, Cursor, VS Code, Cline, and Continue, and can also be used with MCP clients that support HTTP transport.