crisp-plugin-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@crisp-plugin-mcp list my recent Crisp conversations"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
crisp-plugin-mcp
An MCP server with the same tools as Crisp's hosted MCP server (https://api.crisp.chat/mcp/).
It signs in with a Crisp Marketplace plugin token instead of the workspace MCP token.
Crisp's hosted server accepts only the workspace MCP token. Generating that token also replaces the workspace REST API token, which breaks integrations that use the old one. A plugin token leaves the workspace tokens unchanged.
Use
Add the server to your MCP client:
{
"mcpServers": {
"crisp": {
"command": "npx",
"args": ["-y", "crisp-plugin-mcp"],
"env": {
"CRISP_TOKEN_IDENTIFIER": "<plugin token identifier>",
"CRISP_TOKEN_KEY": "<plugin token key>",
"CRISP_WEBSITE_ID": "<website ID>"
}
}
}
}The server needs Node.js 22 or later.
Related MCP server: OpenClaw MCP Proxy
Get a plugin token
Sign in to the Crisp Marketplace.
Create a private plugin.
On the plugin's Tokens page, request a production token with the scopes your tools need. A development token works at once, with a low daily quota.
Install the plugin on your workspace with its private install link.
The website ID is in Crisp under Settings → Workspace Settings → Setup Instructions.
A tool works only when the token has the matching scope. Otherwise the tool returns
Got error reason: 'token_scope_forbidden'. Each call counts against the plugin's daily quota.
How it matches the official server
src/official-tools.jsonis a copy of the official tool list and server instructions. Crisp serves both without authentication. This server lists them unchanged.Each tool calls the Crisp REST API through Crisp's
crisp-apiclient, with plugin-tier authentication.Errors use the official text:
Got error reason: '<reason>'.Results contain the REST API data without
website_idfields, because every tool targets the configured workspace. The official server can shape its results differently.report_feedback_missing_toolhas no REST API route. It returnssent: falseand a note.
Development
mise pins Node and pnpm.
pnpm install, thenpnpm build.pnpm check: format check, lint, typecheck, tests, and Knip.pnpm smoke: start the built server with placeholder credentials and check its tool list.pnpm smoke:live: call read-only tools against the workspace set in the environment.pnpm sync-tools: copy the latest tool list from Crisp. The Git diff onsrc/official-tools.jsonshows what changed. Update the handlers insrc/tools/to match.
Releases are automatic. See docs/releasing.md.
License
MIT
Available Tools
42 toolschange_conversation_stateB
Changes a conversation's state to resolved, unresolved, or pending.
Inputs: session_id (required), state.
create_helpdesk_tree_pathC
Creates a Knowledge Base file at the specified tree_path.
Inputs: tree_path (required), locale, section.
delete_helpdesk_tree_pathB
Deletes the Knowledge Base file at the specified tree_path. Confirm the intended file and path before calling.
Inputs: tree_path (required), locale, section.
get_availability_statusA
Returns the general workspace availability shown to visitors in the chatbox widget (online or offline).
Inputs: no named parameters.
get_conversationA
Returns detailed data and metadata for one conversation. This response may be verbose; use the list_latest_conversation_messages tool if you need messages from that conversation.
Inputs: session_id (required).
get_helpdesk_informationB
Returns basic Knowledge Base information, including its name and URL.
Inputs: no named parameters.
get_helpdesk_settingsA
Returns the Knowledge Base settings. This advanced response may be large; use it when the user asks about Knowledge Base configuration or a specific setting.
Inputs: no named parameters.
get_helpdesk_tree_path_contentB
Returns the content of the Knowledge Base file at the specified tree_path.
Inputs: tree_path (required), locale, section.
get_helpdesk_tree_path_metadataA
Returns the whole metadata of the Knowledge Base file at the specified tree_path. Use the get_helpdesk_tree_path_title tool instead if you only need the title.
Inputs: tree_path (required), locale, section.
get_helpdesk_tree_path_titleB
Returns the title of the Knowledge Base file at the specified tree_path.
Inputs: tree_path (required), locale, section.
get_people_profileA
Returns detailed data for one CRM contact. This response may be verbose; use the search_people_profiles tool first when the contact identifier is not known.
Inputs: people_id_or_email (required).
get_visitors_countA
Returns the number of visitors currently active on the workspace's chatbox widget. This is not a count of visitors currently typing or actively chatting.
Inputs: no named parameters.
get_website_informationC
Returns basic information for the current Crisp workspace.
Inputs: no named parameters.
get_website_settingsA
Returns the workspace's full settings. This advanced response may be large; use it when the user asks about workspace configuration or a specific setting.
Inputs: no named parameters.
list_conversations_at_pageB
Lists conversations in the workspace for one specified page. This tool is paginated, more entries can thus be retrieved.
Inputs: page, inbox_id.
list_helpdesk_localesB
Lists the configured Knowledge Base locales and their public URLs.
Inputs: no named parameters.
list_helpdesk_pagesA
Lists published Knowledge Base page URLs and their tree paths. Prefer the list_helpdesk_tree tool to discover tree_path values for file operations.
Inputs: locale, section.
list_helpdesk_treeA
Lists the Knowledge Base file tree. Use it to discover valid tree_path values for file operations. Recursive traversal is needed to descend deeper in the tree, using the sub_path argument. Descend only if the user asks for a particular content.
Inputs: locale, section, sub_path.
list_inboxesB
Lists the available workspace sub-inboxes, which group conversations together.
Inputs: no named parameters.
list_latest_conversation_messagesA
Lists recent messages for one conversation. Use this when recent context is sufficient instead of retrieving detailed conversation data.
Inputs: session_id (required).
list_latest_conversationsA
Lists recent conversations for the workspace. Use the search_conversations tool when locating conversations by message content or segments.
Inputs: no named parameters.
list_operatorsB
Lists the human operators who are members of the workspace.
Inputs: no named parameters.
list_operators_activeB
Lists workspace operators who are currently active in a Crisp app.
Inputs: no named parameters.
list_people_conversationsA
Lists conversations linked to a CRM contact. Returns conversation session identifiers only; use a conversation tool to inspect their content or metadata.
Inputs: people_id_or_email (required).
list_people_profiles_at_pageB
Lists CRM contacts in the workspace for one specified page. This tool is paginated, more entries can thus be retrieved.
Inputs: page.
list_visitorsB
Lists visitors currently active on the workspace's chatbox widget.
Inputs: no named parameters.
move_conversation_inboxB
Moves a conversation to the specified inbox. Use the list_inboxes tool to discover a valid inbox_id when it is not already known.
Inputs: inbox_id (required), session_id (required).
report_feedback_missing_toolA
Reports feedback to the Crisp team about something missing or broken on this MCP server. This tool should be suggested to the user if the AI agent gets stuck. An action_trace should be provided.
Inputs: action_trace (required).
search_conversationsA
Searches workspace conversations by message content or conversation segments. Use this when locating a conversation by content or segment rather than recency.
Inputs: search_query (required), search_in.
search_helpdesk_treeA
Searches the expanded Knowledge Base file tree by file title. Use it to locate a file when its path is unknown; no recursive traversal is needed.
Inputs: search_query (required), locale, section.
search_people_profilesA
Searches CRM contacts by full name or email address. Use this to find a person record; use the search_conversations tool to find a conversation.
Inputs: search_query (required).
send_conversation_message_noteB
Adds an internal note to an existing conversation. Notes are visible only to workspace operators and are not sent to the recipient. They stay private to your team at any time.
Inputs: text (required), session_id (required), mentions.
send_conversation_message_textA
Sends a customer-visible text message to the recipient in an existing conversation.
Inputs: text (required), session_id (required).
set_conversation_emailC
Sets the contact's email address in a conversation's metadata.
Inputs: email (required), session_id (required).
set_conversation_full_nameC
Sets the contact's full name in a conversation's metadata.
Inputs: full_name (required), session_id (required).
set_conversation_phoneB
Sets the contact's phone number in a conversation's metadata.
Inputs: phone (required), session_id (required).
update_helpdesk_tree_path_contentC
Updates the content of the Knowledge Base file at the specified tree_path.
Inputs: content (required), tree_path (required), locale, section.
update_helpdesk_tree_path_titleC
Updates the title in the metadata of the Knowledge Base file at the specified tree_path.
Inputs: title (required), tree_path (required), locale, section.
update_people_profile_emailB
Updates the email address of a specific CRM contact.
Inputs: new_email (required), people_id_or_email (required).
update_people_profile_full_nameC
Updates the full name of a specific CRM contact.
Inputs: full_name (required), people_id_or_email (required).
update_people_profile_phoneC
Updates the phone number of a specific CRM contact.
Inputs: phone (required), people_id_or_email (required).
update_people_profile_segmentsB
Updates the segments of a specific CRM contact.
Inputs: segments (required), people_id_or_email (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 42 tools
Most tools target clearly distinct resource+action pairs, and descriptions actively disambiguate the tricky ones (e.g. list_latest_conversations vs search_conversations, list_helpdesk_pages vs list_helpdesk_tree). The main risk is the parallel set_conversation_* vs update_people_profile_* families, which operate on different resources but look similar at a glance.
Nearly all tools follow a snake_case verb_noun pattern (list_, get_, update_, create_, delete_, search_). Minor deviations exist: 'change_conversation_state' and 'move_conversation_inbox' use different verbs than the set_/update_ families for analogous metadata operations, and 'send_conversation_message_text' has an unusual noun ordering.
42 tools is heavy for a single MCP server and exceeds the 25+ threshold where surface area becomes a burden. While the domain is broad (helpdesk, conversations, CRM, workspace), several granular getters/setters (title, metadata, content, email, phone) could be consolidated.
Coverage is strong across Knowledge Base CRUD, conversation lifecycle (list/search/get/messages/send/state/inbox), CRM profiles, and workspace info. Gaps remain: no create/delete for conversations or people profiles, and no operator management beyond listing.
Maintenance
Related MCP Connectors
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
Toolstile is a managed MCP gateway that connects remote MCP servers behind one endpoint, with per-agent permissions, shared accounts and activity logs. Connect at https://mcp.toolstile.com/mcp over Streamable HTTP with OAuth; sign in at https://toolstile.com, select a workspace and connect your upstream servers. Available tools, resources and prompts depend on that workspace and the agent's granted access.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that exposes fixed tools for GPT, Claude, and Gemini while routing to any OpenAI-compatible chat completions backend with independent configuration per target.1-
- FlicenseNot gradedqualityDmaintenanceExposes app-registered tools as an MCP server for OpenClaw, forwarding actual tool execution back to the app over a WebSocket bridge.-
- AlicenseNot gradedqualityBmaintenanceSelf-hosted workspace MCP gateway that registers MCP servers, stores secrets encrypted, mints agent keys, and shares a unified tool library across multiple AI harnesses.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables external AI applications to access MCP tools by providing a user-hosted HTTPS endpoint that forwards requests to a paired desktop client.MIT