Crisp MCP server: community

How to connect Crisp MCP to Claude Desktop

Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.

{
  "mcpServers": {
    "crisp": {
      "command": "npx",
      "args": ["mcp-remote", "<YOUR_MCP_URL>"]
    }
  }
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://app.hugo.ai/api/mcp/
// Claude Code (one-liner): claude mcp add crisp <YOUR_MCP_URL> --transport http

Some MCP servers require an API key. Check the source page for setup: app.hugo.ai/api/mcp.

Does Crisp MCP cost extra?

Community (free)

The Crisp MCP server is community-built — free to run, but you still pay for your Crisp subscription.

Community MCPs are normally self-hosted from a GitHub repo. There's no extra license fee.
Your Crisp account still needs whatever plan is required to access the data the MCP server queries.
Trade-off: zero MCP cost, but no guarantee it'll keep working when Crisp changes their UI or API.

MCP cost

Free (self-hosted)

Subscription required

Yes (your tool plan)

Maintained by

Community

Crisp also publishes a REST API

Crisp publishes an API, but per-tier gating wasn't extracted automatically.

API docs

—

Auth method

—

SDK languages

—

OpenAPI spec

—

Webhooks

—

Structured outputs

—

See Crisp API page

What you can do with Crisp from an AI agent

Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.

INDIE / SOLO

Skip the dashboard, ask Claude

"What changed this week?" answered in seconds
Quick one-off questions without leaving the editor
Pipe Crisp data into your personal notes / docs without writing a script

Effort: 30 seconds — paste the config, restart Claude

AGENCY

Run client analysis at agent speed

Hand the MCP server to your team — every consultant can ask Claude about any client's Crisp account
Multi-account workflows without context-switching the Crisp UI
Reports you'd normally spend hours on, done before standup

Effort: An afternoon — set up auth per client

IN-HOUSE TEAM

Production agent workflows

Embed in your internal Codex / Cursor agents that triage Crisp data daily
Combine with other MCP servers in a multi-step agent chain
Constrain agents to read-only roles to keep production Crisp safe

Effort: Days — security review + role config

Limits and gotchas

Official MCP server — published by Crisp themselves, so it should track product changes.
Fallback: the REST API works for any flow the MCP server doesn't cover.
Rate limits: MCP calls count against your underlying Crisp API quota. Burst usage from a curious agent can drain a daily allowance fast.

6/10

Agent-readiness verdict

Scored by Joonas (TMB).

Crisp MCP & API FAQ

Is the Crisp MCP server official?+

Yes — an official, vendor-maintained server at null.

Can I use the Crisp MCP with Cursor or Codex?+

Yes — MCP is a protocol, not Claude-specific. Any MCP-capable client (Cursor, Codex, Windsurf, Zed) can use the same server config with minor path adjustments.

Sources

Crisp official site: https://crisp.chat/
MCP server page: https://app.hugo.ai/api/mcp/

Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.

Joonas RotkoAuthor & Founder of That Marketing Buddy

10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.

About me How I review

Crisp MCP Server

What is the Crisp MCP server?

What you can build with the Crisp MCP