Customer support, live chat, CRM and helpdesk on Crisp with the full official REST API v1 (api.crisp
Scored across 7 tools
The set has major overlap: `marketplace` and `search_tools` both offer search/describe/invoke catalog actions, making it unclear which to call. `report_bug` is also called out as a capability inside `marketplace`, blurring whether that tool is the action or the top-level one.
All names are lowercase with underscores, but they mix verb-oriented names (`authenticate`, `connect`, `report_bug`) with noun-oriented names (`marketplace`, `search_tools`) and no consistent verb_noun pattern. `show_version` and `toolkit_info` are similarly status-like but follow different naming styles.
Seven tools is within a reasonable range and the count itself is not problematic. However, the `marketplace` tool is overloaded with many sub-capabilities and `search_tools` duplicates part of it, so the effective scope feels less clean than the raw count suggests.
The main workflows are covered: authentication, connection status, catalog search, account/toolkit state, and bug reporting. Missing pieces like an obvious way to uninstall/disconnect or list callable tools are hidden inside `marketplace`, but these are workable gaps rather than fatal ones.
MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header Authorization: Bearer <token> for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "" } after the user pastes, or with no args to get the link.
Inputs: token.
Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
Inputs: no named parameters.
The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/ link that opens without login.
Inputs: limit, query, action, mcp_id, +19 more.
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
Inputs: message (required), context, conversation.
Single entrypoint for MCP catalog. action=search returns available tools ordered by relevance. action=describe returns tool schema. action=invoke executes a tool by ID.
Inputs: query, action, queries, tool_id, +3 more.
Show the current MCP platform and adapter versions.
Inputs: no named parameters.
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Manage HelpCrunch chats, customers, agents and knowledge-base articles.
Manage Teletype support conversations, customers, messages, and workspace settings
Manage Customerly contacts, conversations, companies, segments and knowledge base
Your own CRM, fully customizable and agent-driven. Start with contacts, companies and a sales pipeli
Add one secure layer between your agents and this server.
