Crisp MCP server
Crisp in any MCP client, through Memtro: Crisp does not publish this server. Memtro's Crisp connector reads Crisp through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Crisp inbox: conversations by state, unread or assignee with their last message, full message threads, contact profiles (company, segments, notes), the website's operators and contact count; can also send a message or a private note, resolve or reopen a conversation, assign it, set its contact details, subject and segments, move it to another inbox, block a visitor, email a transcript, delete a conversation, and create, update, add timeline events to or delete a contact profile, when you ask.
Reads
crisp_websiteThe connected Crisp website: name and domain, its operators (name, email, role, availability) and how many contacts it holds.crisp_conversationsCrisp conversations, most recently updated first: state (pending, unresolved, resolved), the visitor's name, email and segments, assignee…crisp_conversationOne Crisp conversation by session id with its messages, oldest first: who wrote each (user = the visitor, operator = your team…crisp_peopleSearch Crisp contact profiles by email or name, or by segment: name, email, phone, company, role, location, segments, notes, engagement score…
Acts, when you ask
These change something in Crisp. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
crisp_send_messageSends a message in a Crisp conversation as an operator — the visitor receives it on their channel — or, with as_note: true…crisp_set_conversation_stateResolves, reopens (unresolved) or marks pending a Crisp conversation.crisp_assign_conversationAssigns a Crisp conversation to an operator (user id from crisp_website), or unassigns it with unassign: true.crisp_update_conversationSets a Crisp conversation's contact details and labels: the visitor's name, email, phone and address, the conversation subject, its segments…crisp_move_conversation_inboxMoves a Crisp conversation to another inbox of the website (by inbox id).crisp_block_conversationBlocks (or with blocked: false unblocks) a visitor's further messages in a Crisp conversation.crisp_email_transcriptHas Crisp email the whole history of a conversation, the visitor's messages included, to the token's user or an operator…crisp_delete_conversationRemoves a Crisp conversation and its messages from the website.crisp_create_personCreates a Crisp contact profile with an email and name, and optionally phone, company, job title, segments and private notes.crisp_update_personUpdates a Crisp contact profile (by people id or email): email, name, phone, company, job title, segments (replacing them) or private notes.crisp_add_person_eventAdds an event (a line of text, optional colour and data) to a Crisp contact's timeline, seen by operators on the profile.crisp_delete_personRemoves a Crisp contact profile (by people id or email).
Connect it
First connect Crisp on Dashboard → Connections, then add Memtro to your client once. The Crisp tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Crisp connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which conversations are unresolved and unread right now, and who are they assigned to?
- › What did Lee Fenwick say in their last conversation with us?
- › Which contacts in the Enterprise segment have been active this week?
- › Assign the conversation with lee@brightpath.io to Ana and mark it resolved
- › Send a note on that conversation for the team: customer is on the annual plan, do not offer the monthly discount
Questions
- Is this an official Crisp MCP server?
- No. It is Memtro's MCP server with Memtro's Crisp connector behind it: the connector reads Crisp through its API with the credentials you connect on Dashboard → Connections, and Crisp publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Crisp?
- Only when you ask, and only what it has been granted: send a message, or a private operator note, in a conversation; resolve, reopen or mark a conversation pending; assign a conversation to an operator, or unassign it; set a conversation's contact name, email, phone, subject, segments or data; move a conversation to another inbox; block or unblock a visitor's further messages; email a conversation's transcript to an operator or an address; delete a conversation permanently; create or update a contact profile, or add an event to its timeline; delete a contact profile permanently. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.