Crisp
Crisp is a customer messaging platform for managing conversations, contacts, operators, helpdesk content, campaigns, and workspace settings.
Verdict
Common use cases
- Triage unassigned support tickets at shift start
- Pull customer conversation history before a call
- Assign high-priority conversations to available operators
- Search profiles by email to check subscription tier
- Audit open conversations by inbox at standup
Integration
- Vendor
- Crisp
- Category
- other
- Auth
- API_KEY
- Tools
- 12
- Composio slug
crisp
Tools
- Assign Conversation
Assign a conversation to one operator or explicitly remove its current operator assignment.
- Get Conversation
Get one conversation's status, assignment, inbox, visitor metadata, unread counts, and latest-message summary.
- Get People Profile
Get one customer profile by its Crisp people ID or exact email address.
- List Conversation Messages
Return a batch of messages from a conversation, optionally before, after, or around one millisecond timestamp.
- List Conversations
List or search workspace conversations with support-focused filters, one page at a time.
- List Inboxes
List configured Crisp inboxes and their operator/team membership, one page at a time.
- List Operators
List workspace operators and pending members with their IDs, roles, and current availability.
- List People Profiles
List or search customer profiles by text, creation date, and sort order, one page at a time.
- Move Conversation to Inbox
Move a conversation to a specific Crisp inbox, or remove its inbox categorization when inbox_id is null.
- Send Conversation Message
Send a visitor-visible text reply to an existing Crisp conversation immediately; this external communication is irreversible.
- Update Conversation Meta
Update support-relevant visitor details, subject, segments, or custom data on a conversation without replacing unspecified fields. Provide at least one field to update.
- Update Conversation State
Set a conversation to pending, unresolved, or resolved.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and click Integrations, then find Crisp in the MCP directory. 2. Click Connect and you'll see a prompt for your Crisp API credentials—open a new tab, log into your Crisp dashboard, navigate to Settings > API, and generate a new key pair (identifier and secret key). 3. Copy both values back into Switchy's connection form and click Authorize. 4. Switchy will verify the credentials and list the 12 tools now available. 5. To test, create a Project, type '@Crisp list the five most recent unassigned conversations' and send—if you see conversation IDs and snippets, the connection works. 6. Inside any Project, @mention Crisp by name to invoke tools like searching profiles, assigning tickets, or retrieving message threads.
What teammates see: by default, memories from Crisp are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Triage Open Tickets
@Crisp list the ten oldest unassigned conversations in our main inbox, sorted by creation date ascending.
Prep for Customer Call
@Crisp get the people profile for alice@example.com, then list all messages in her most recent conversation.
Assign Urgent Conversation
@Crisp list operators who are currently available, then assign conversation ID abc123 to the first one.
Audit Inbox Load
@Crisp list all inboxes, then for each inbox show me how many unresolved conversations are currently open.
Search Customer by Email
@Crisp get the people profile for bob@company.com and summarize their last three conversations.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@crisp list all unresolved conversations from the last 48 hours and group them by inbox
Found 23 unresolved conversations across 3 inboxes. **Sales inbox** (12 conversations): 8 assigned to operators, 4 unassigned. Oldest unread from 41 hours ago. **Support inbox** (9 conversations): 6 assigned, 3 unassigned. Two conversations marked urgent. **Billing inbox** (2 conversations): both assigned, average response time under 2 hours. All timestamps reflect your workspace's UTC offset; unread counts include both visitor and internal notes.
This example combines list-conversations filtering with inbox metadata to surface triage priorities. Requires read access to conversations and inboxes. Crisp's API pages results; if your workspace handles high message volume, the MCP fetches one page at a time and may not return every conversation in a single call.
@crisp assign conversation e89f3c2a to operator julie@example.com and add a note that this customer mentioned enterprise pricing
Conversation e89f3c2a reassigned to Julie Chen (julie@example.com, operator ID op_7x4k). Previous assignment to Sam removed. Internal note added: 'Customer mentioned enterprise pricing — flagged for follow-up.' Note visible only to operators. Visitor will see Julie as the new responder if they send another message. Assignment change logged in conversation timeline.
Demonstrates write actions that change conversation state and add operator context. Requires operator-write permissions in your Crisp workspace. The MCP does not send a message to the visitor; assignment changes are internal unless an operator replies. Use this to route high-value leads or escalations without leaving Switchy.
@crisp pull the last 20 messages from conversation a4b9f12c and draft a two-sentence handoff summary for the next operator
Retrieved 20 messages spanning 6 hours. Visitor (Emma, emma.torres@startup.io) reported login failures on staging environment; operator confirmed API key expiration and sent new credentials 40 minutes ago. Visitor acknowledged receipt but has not confirmed resolution. **Handoff summary**: Emma received replacement API keys for staging after expiration caused login errors. Follow up in 2 hours to confirm access restored and close ticket if resolved.
Shows how the MCP's message-retrieval pairs with the AI's summarization to compress conversation context. Useful when operators switch mid-thread or you need to brief a manager. Message timestamps and sender metadata help the AI distinguish visitor questions from operator replies. Rate-limit-aware: fetching messages from high-traffic conversations may require multiple calls.
Use-case deep-dives
When Crisp MCP wins for 24-hour support handoffs
A 6-person support team split across San Francisco and Berlin uses Crisp for customer chat. At 9am Pacific, the EU shift ends and the US shift starts. The Assign Conversation and List Conversations tools let the outgoing operator write a Switchy prompt that auto-assigns their 4 open threads to the right US teammate based on conversation tags and customer tier. Get Conversation pulls the last 3 messages so the handoff note includes context. This works when your team runs under 30 concurrent chats and operators trust AI to read tags correctly. Above that volume, you need a dedicated ticketing system with SLA routing. If your handoff is once a day and the context lives in Crisp metadata, this MCP closes the loop without a second tool.
When this MCP helps account managers prep renewal meetings
A 3-person account team at a B2B SaaS company runs quarterly business reviews with 40 enterprise customers. Two days before each QBR, the account manager asks Switchy to pull the customer's Crisp profile and last 90 days of conversation history. Get People Profile surfaces the contact's metadata and lifecycle stage. List Conversation Messages returns support threads so the AM can spot recurring pain points or feature requests. This scenario works when your support volume is under 200 conversations per customer per quarter and your team already uses Crisp as the system of record. If support lives in Zendesk or Intercom instead, this MCP won't see the data. For teams that close 10-20 renewals a month and want AI to write the prep doc, Crisp MCP is the direct path.
When Crisp MCP helps a solo founder handle launch-day volume
A solo technical founder launches a new API product and gets 60 inbound Crisp chats in 8 hours. List Conversations with filters pulls threads tagged 'billing' or 'bug' into Switchy. Get Conversation shows which ones have been waiting over 2 hours. The founder writes a prompt that drafts replies to the 12 billing questions using the same FAQ answer, then flags the 5 bug reports for engineering follow-up. This works when the spike is under 100 chats and the founder can review AI drafts before sending. If you're fielding 200-plus chats or need multi-agent routing, Crisp's native automation is faster than MCP orchestration. For the occasional launch-day crunch at a 1-3 person company, this MCP turns Switchy into a triage co-pilot without hiring a support lead.
Frequently asked
What does the Crisp MCP do in Switchy?
It lets your AI agents read customer conversations, assign tickets to operators, look up visitor profiles, and search message history across your Crisp workspace. Agents can pull conversation context, check operator availability, and route support requests without opening the Crisp dashboard. It doesn't send replies on behalf of operators—use Crisp's own interface for that.
Do I need admin access to connect Crisp?
You need a Crisp API key with read and write permissions on conversations, people profiles, and workspace settings. Typically only workspace owners or admins can generate keys with those scopes. If you're an operator without admin rights, ask your workspace owner to create the key and share it with you.
Can the MCP send messages to customers in Crisp?
No. The twelve tools focus on reading conversation data, assigning tickets, and searching profiles. If your agent needs to reply to a customer, it can draft the message in Switchy and hand it to a human operator who sends it through Crisp. This keeps your support tone consistent and avoids accidental bot replies.
Why use this instead of Crisp's chatbot builder?
Crisp's built-in bots handle simple flows inside the widget. This MCP pulls conversation data into Switchy where your agents can combine it with data from Slack, Notion, or GitHub—useful for escalations that need context from multiple tools. Use Crisp bots for front-line triage; use this MCP when your agent needs cross-tool intelligence.
Who on the team should connect the Crisp MCP?
Whoever manages your support workflow and has admin access to generate API keys. Once connected, any Switchy teammate can ask agents to search conversations or check operator availability. The MCP doesn't count against Crisp's operator seats, but every API call uses your workspace's rate limit.