MCP server for interacting with your LINE Official Account
Nothing to run from here
Helpcrunch is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
12
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Manage HelpCrunch chats, customers, agents and knowledge-base articles.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http usefulapi-helpcrunch-mcp https://helpcrunch.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# helpcrunch_list_customers, helpcrunch_get_customer, helpcrunch_list_chats and 9 more
Helpcrunch costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http usefulapi-helpcrunch-mcp https://helpcrunch.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| field | string | no | Field to filter on (e.g. customers.email, chats.status). |
| operator | string | no | Filter comparison operator (used with field + value). |
| value | string | no | Value to compare the field against (used with field + operator). |
| sort | string | no | Field to sort by, e.g. customers.firstSeen / customers.lastSeen. |
| order | string | no | Sort direction. |
| limit | integer | no | Max records to return (pagination limit). |
| offset | integer | no | Records to skip (pagination offset). |
Get a single customer by id. HelpCrunch REST: GET /customers/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The customer id (numeric id, passed as a string). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| field | string | no | Field to filter on (e.g. customers.email, chats.status). |
| operator | string | no | Filter comparison operator (used with field + value). |
| value | string | no | Value to compare the field against (used with field + operator). |
| sort | string | no | Field to sort by, e.g. chats.createdAt. |
| order | string | no | Sort direction. |
| limit | integer | no | Max records to return (pagination limit). |
| offset | integer | no | Records to skip (pagination offset). |
Get a single chat (conversation) by id. HelpCrunch REST: GET /chats/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The chat id (numeric id, passed as a string). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The chat id (numeric id, passed as a string). |
| limit | integer | no | Max messages to return (max 100). |
| offset | integer | no | Records to skip (pagination offset). |
List agents (support staff / operators) in the account, with role and email. Paginate with limit/offset. HelpCrunch REST: GET /agents.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max records to return (pagination limit). |
| offset | integer | no | Records to skip (pagination offset). |
List departments (groups of agents that chats can be routed to), each with its agents. Paginate with limit/offset. HelpCrunch REST: GET /departments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max records to return (pagination limit). |
| offset | integer | no | Records to skip (pagination offset). |
List applications configured in the account — web chat widgets, iOS/Android apps, and social integrations (id, name, displayName, active, type). HelpCrunch REST: GET /applications.
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chat | integer | yes | The chat id to post the message into. |
| text | string | yes | The message text. |
| type | string | no | "message" = customer-visible reply; "private" = internal note. |
| agent | integer | no | Agent id — required for agent messages; omit for customer messages. |
| markdown_text | string | no | Optional markdown version of the message (→ markdownText). |
CHANGES the status of a LIVE chat (e.g. mark it opened, pending, on hold, or closed). HelpCrunch REST: PUT /chats/status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | The chat id to update. |
| status | string | yes | The new chat status. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | The chat id to (re)assign. |
| assignee | integer | no | Agent id to assign the chat to. Omit (or null) to unassign. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Helpcrunch or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Helpcrunch can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.