crisp-mcp-server

An Model Context Protocol server for the Crisp REST API, deployed on Cloudflare Workers.

It exposes Crisp websites, operators, and conversations as MCP tools so an MCP-compatible AI agent can query them, post private notes, and manage conversation segments.

Tools

Related MCP server: neon-mcp

Authentication

The server is stateless and credential-free: it does not store any Crisp token. Each MCP client passes the Crisp token directly to the endpoint.

The Crisp REST API uses Basic auth with a keypair token_id:token_key. Base64-encode the string token_id:token_key and pass it as a Bearer token to the MCP endpoint:

Authorization: Bearer <base64(token_id:token_key)>

The worker forwards that value as Authorization: Basic <base64(...)> to the Crisp API.

Tier

Crisp tokens are either website (single workspace) or plugin (multi-workspace). Select the tier with the tier query parameter:

• ?tier=website (default) — sets X-Crisp-Tier: website

• ?tier=plugin — sets X-Crisp-Tier: plugin

Generate tokens from the Crisp app: Settings → Workspace Settings → Advanced configuration → API Token (website), or the Crisp Marketplace (plugin).

Develop

npm install
npm run dev      # local dev at http://localhost:8787
npm run typecheck

Deploy

npm run deploy

Then point an MCP client at https://<your-worker>.workers.dev/mcp?tier=website with the Authorization: Bearer <base64(...)> header.

Claude Desktop / Claude Code example

{
  "mcpServers": {
    "crisp": {
      "url": "https://<your-worker>.workers.dev/mcp?tier=website",
      "headers": {
        "Authorization": "Bearer <base64(token_id:token_key)>"
      }
    }
  }
}

How it works

• src/index.ts — Worker entry. Extracts the Bearer token and tier from the request, builds a fresh MCP server per request, and hands it to createMcpHandler (stateless Streamable HTTP transport).

• src/crisp.ts — Thin read-only Crisp REST client (https://api.crisp.chat/v1).

• src/tools.ts — Registers the MCP tools above.

Notes

• Read-mostly: only private notes and conversation segments are writable; all other tools are read-only.

• Stateless: no Durable Objects, no sessions, no stored credentials.

• The Crisp token is sent by the client on every connection; rotate it from the Crisp app if leaked.