Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CRISP_TOKEN_KEYYesThe plugin token key.
CRISP_WEBSITE_IDYesThe Crisp website ID.
CRISP_TOKEN_IDENTIFIERYesThe plugin token identifier.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Introduction

This server provides access to the authenticated Crisp workspace.

General instructions

Safety

You may use read-only discovery tools without confirmation when needed to complete the request. Do not retrieve advanced, broad, or sensitive configuration unless the user explicitly requests it or it is necessary for their request.

Perform a write only after explicit user confirmation. A direct request that clearly specifies the intended change counts as confirmation. Otherwise, summarize the exact proposed change and ask for confirmation.

Before a destructive action, obtain two separate explicit confirmations. In the second confirmation, state the affected resource and that data loss can occur.

Tool calls

Use read-only tools first when you need to identify a website, conversation, contact, or other resource. Do not guess resource IDs or workspace ownership. If discovery returns multiple plausible matches, ask the user to choose.

Some list and search tools may return partial results or apply an internal page limit. Do not claim results are complete unless the tool explicitly says so. Offer additional retrieval only when the tool provides a page parameter or continuation value. You will not know if there are more results, unless you try the next page (only try if the previous page yielded at least 1 result). Stop when the next page has no result at all. Confirm with the user if paginating too far away (after looping on 5 pages, confirm to loop on next 5 pages — if you require it).

If a tool accepts a page input argument, and responds with a pagination output object, containing pagination.is_partial_result = true, then read pagination.next_page and use this as the next page for the page input argument if you need to paginate to the next page. Stop iterating on next page if pagination.is_partial_result = false or pagination.next_page = null.

Group instructions

Tools are grouped by the resource they touch; the largest groups are conversations, people, and helpdesk. Those group names are included in tool names, for example send_conversation_message_text.

Conversations

  • Conversations are identified by their session_id, which is an opaque identifier.

  • Discover the session_id first if the user does not explicitly provide it. Do not ask the user for a session_id if it is not provided; always discover it using list or search tools.

People

  • People CRM profiles are identified by a people_id, also referred to as people_id_or_email. This value accepts either an opaque identifier or an email address for the CRM contact. Prefer using the email address unless you already know the opaque identifier (people_id) from the contact list or search results.

  • If the user provides an email address, there is no need to discover the people_id.

Helpdesk

  • Helpdesk entries are identified by the tuple (locale, section, tree_path). For English, the locale is en. The section is the content type, usually articles. The tree path is a filesystem-like path to a directory or file, usually a Markdown file such as path/to/article.md.

  • The user provides the locale and section, but you may need to discover the tree_path. To do so, call the list or search tree-path tools and descend through the results, as these routes are tree-path-prefix-based, like a file explorer on a PC where you open folders and subfolders.

  • When descending tree-path lists for discovery, generate the final tree path by concatenating each individual tree-path slug with slashes. For example, first-level and second-level.md become first-level/second-level.md; use this as the final tree_path value in tool calls.

Miscellaneous

If a user-requested action cannot be completed using the available tools, suggest that they use the report_feedback_missing_tool tool to report the issue to the Crisp team. Let them know that the Crisp team can quickly add tools to fill the gap. Provide a concise, auto-generated trace based on the context without leaking any private information. This will be used by the Crisp technical team to improve the MCP server.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_website_informationC

Returns basic information for the current Crisp workspace.

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.

get_availability_statusA

Returns the general workspace availability shown to visitors in the chatbox widget (online or offline).

list_operatorsB

Lists the human operators who are members of the workspace.

list_operators_activeB

Lists workspace operators who are currently active in a Crisp app.

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.

list_visitorsB

Lists visitors currently active on the workspace's chatbox widget.

list_inboxesB

Lists the available workspace sub-inboxes, which group conversations together.

list_latest_conversationsA

Lists recent conversations for the workspace. Use the search_conversations tool when locating conversations by message content or segments.

list_conversations_at_pageB

Lists conversations in the workspace for one specified page. This tool is paginated, more entries can thus be retrieved.

search_conversationsA

Searches workspace conversations by message content or conversation segments. Use this when locating a conversation by content or segment rather than recency.

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.

send_conversation_message_textA

Sends a customer-visible text message to the recipient in an existing conversation.

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.

set_conversation_full_nameC

Sets the contact's full name in a conversation's metadata.

set_conversation_emailC

Sets the contact's email address in a conversation's metadata.

set_conversation_phoneB

Sets the contact's phone number in a conversation's metadata.

change_conversation_stateB

Changes a conversation's state to resolved, unresolved, or pending.

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.

list_latest_conversation_messagesA

Lists recent messages for one conversation. Use this when recent context is sufficient instead of retrieving detailed conversation data.

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.

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.

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.

update_people_profile_full_nameC

Updates the full name of a specific CRM contact.

update_people_profile_emailB

Updates the email address of a specific CRM contact.

update_people_profile_phoneC

Updates the phone number of a specific CRM contact.

update_people_profile_segmentsB

Updates the segments of a specific CRM contact.

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.

get_helpdesk_informationB

Returns basic Knowledge Base information, including its name and URL.

list_helpdesk_localesB

Lists the configured Knowledge Base locales and their public URLs.

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.

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.

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.

create_helpdesk_tree_pathC

Creates a Knowledge Base file at the specified tree_path.

delete_helpdesk_tree_pathB

Deletes the Knowledge Base file at the specified tree_path. Confirm the intended file and path before calling.

get_helpdesk_tree_path_contentB

Returns the content of the Knowledge Base file at the specified tree_path.

update_helpdesk_tree_path_contentC

Updates the content of the Knowledge Base file at the specified tree_path.

get_helpdesk_tree_path_titleB

Returns the title of the Knowledge Base file at the specified tree_path.

update_helpdesk_tree_path_titleC

Updates the title in the metadata of the Knowledge Base file at the specified tree_path.

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.

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.

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 42 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count2/5

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.

Completeness4/5

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

ActivityMaintained
ResponsivenessNo recent community issues