HelpCrunch MCP server. Manage HelpCrunch chats, customers, agents and knowledge-base articles.
Add to your MCP config, then reload & authorize:
{
"mcpServers": {
"helpcrunch": {
"url": "https://helpcrunch.usefulapi.io/mcp"
}
}
}| Tool | Type | What it does |
|---|---|---|
helpcrunch_list_customers | read | List customers List / search customers (people who chatted in). Optionally filter with a single field/operator/value clause (comparison AND), sort (e.g. customers.firstSeen, customers.lastSeen) with order, and paginate with limit/offset. HelpCrunch REST: POST /customers/search. |
helpcrunch_get_customer | read | Get customer Get a single customer by id. HelpCrunch REST: GET /customers/{id}. |
helpcrunch_list_chats | read | List chats List / search chats (conversations). Optionally filter with a single field/operator/value clause (comparison AND), sort (e.g. chats.createdAt) with order, and paginate with limit/offset. HelpCrunch REST: POST /chats/search. |
helpcrunch_get_chat | read | Get chat Get a single chat (conversation) by id. HelpCrunch REST: GET /chats/{id}. |
helpcrunch_get_chat_messages | read | Get chat messages Get the messages of a chat (conversation), newest first (sorted by createdAt DESC). Paginate with limit (max 100) / offset. HelpCrunch REST: GET /chats/{id}/messages. |
helpcrunch_list_agents | read | List agents List agents (support staff / operators) in the account, with role and email. Paginate with limit/offset. HelpCrunch REST: GET /agents. |
helpcrunch_list_departments | read | List departments List departments (groups of agents that chats can be routed to), each with its agents. Paginate with limit/offset. HelpCrunch REST: GET /departments. |
helpcrunch_list_applications | read | List applications List applications configured in the account — web chat widgets, iOS/Android apps, and social integrations (id, name, displayName, active, type). HelpCrunch REST: GET /applications. |
helpcrunch_get_organization | read | Get organization Get the organization's live-chat availability status — domain, whether the team is online (teamOnline), and whether chat is enabled (chatEnabled). HelpCrunch REST: GET /organization. |
helpcrunch_create_message | write | Create message POSTS a message into a LIVE chat — a customer-visible reply (type "message") or an internal private note (type "private"). Set `agent` (agent id) for agent messages; omit it for customer messages. HelpCrunch REST: POST /messages. |
helpcrunch_update_chat_status | write | Update chat status CHANGES the status of a LIVE chat (e.g. mark it opened, pending, on hold, or closed). HelpCrunch REST: PUT /chats/status. |
helpcrunch_assign_chat | write | Assign chat ASSIGNS (or unassigns) a LIVE chat to an agent. Pass `assignee` (agent id) to assign; omit it (or pass null) to unassign. HelpCrunch REST: PUT /chats/assignee. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.