MCP server for interacting with your LINE Official Account
Nothing to run from here
SupportBee MCP by usefulapi 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.
22
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read SupportBee tickets, replies and reports; reply, comment, label, assign and archive tickets.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http supportbee-mcp-by-usefulapi https://supportbee.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# supportbee_list_tickets, supportbee_search_tickets, supportbee_get_ticket and 19 more
SupportBee MCP by usefulapi 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 supportbee-mcp-by-usefulapi https://supportbee.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
22 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 tickets of the shared inbox, newest activity first, with filters (assignee, team, label, requester, dates, spam/trash/archived). By default archived, spam and trashed tickets are left out. Each ticket has id, subject, labels, requester, assignee, replies_count, comments_count, unanswered, archived and the first message text (cut). With total_only=true only the number of matching tickets comes
| Parameter | Type | Required | Notes |
|---|---|---|---|
| archived | string | no | true = only archived tickets, false = no archived tickets (default), any = both. |
| spam | boolean | no | Include tickets marked as spam (default false). |
| trash | boolean | no | Include trashed tickets (default false). |
| has_replies | boolean | no | true = only tickets that have replies, false = only tickets without replies. |
| max_replies | integer | no | Only tickets with this number of replies (not with has_replies=false). |
| assigned_user | string | no | me = assigned to the token's user, an agent id (from supportbee_list_users), any = assigned to someone, none = unassigned. |
| assigned_team | string | no | mine = assigned to the user's teams, a team id (from supportbee_list_teams), none = no team. |
| label | string | no | Only tickets with this label name (supportbee_list_labels). |
| since | string | no | Only tickets with last activity after this time (date, ISO date-time or Unix timestamp). |
| until | string | no | Only tickets with last activity before this time (date, ISO date-time or Unix timestamp). |
| sort_by | string | no | Sort order (default last_activity). |
| requester_emails | array | no | Only tickets from these requester e-mail addresses (max 10). |
| total_only | boolean | no | Return only the total number of matching tickets. |
| per_page | integer | no | Tickets per page, 1-99 (default 15). |
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
Full-text search over tickets (subject, body, requester) with SupportBee's search syntax, newest activity first. Spam and trash are excluded unless asked. GET /tickets/search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | The search keywords or query. |
| spam | boolean | no | Include tickets marked as spam (default false). |
| trash | boolean | no | Include trashed tickets (default false). |
| per_page | integer | no | Tickets per page, 1-99 (default 15). |
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
One ticket with subject, requester, labels, assignees, state and the first message text. Replies and comments are separate calls. GET /tickets/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
The public replies (the conversation with the customer) of a ticket, oldest first, as text. GET /tickets/{id}/replies.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
One reply of a ticket (text, replier, cc/bcc). GET /tickets/{ticket_id}/replies/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
| reply_id | integer | yes | The reply id (from supportbee_list_replies). |
The internal comments (visible to agents only, never e-mailed) of a ticket, oldest first, as text. GET /tickets/{id}/comments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
What happened to a ticket and who did it (assignments, label changes, replies, archiving) with timestamps. GET /tickets/{id}/audit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
All custom labels of the company (name and color). Use a label name with supportbee_add_label or the label filter. GET /labels.
No parameter schema on file.
The teams of the company (id, name), optionally only those that have users in them, or only the token user's teams. GET /teams.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| with_users | boolean | no | Only teams that have users in them (SupportBee's with_users filter; it does not add the member list). |
| mine_only | boolean | no | Only the teams of the user who owns the token. |
The agents, admins and collaborators of the desk (id, name, e-mail, role, teams), or customer groups. Use the id as assigned_user or user_id. GET /users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | user (default) or customer_group. |
| with_roles | array | no | Roles to include (default admin, agent, collaborator). |
| with_invited | boolean | no | Include users who were invited but have not joined yet (default false). |
One user or customer with role, teams, ticket counts and a few of their recent tickets. GET /users/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_id | integer | yes | The user id (from supportbee_list_users). |
| max_tickets | integer | no | How many of the user's tickets to include (default 5). |
The canned replies (snippets) of the company: name, tags and text, to reuse in a reply. GET /snippets.
No parameter schema on file.
The support e-mail addresses (forwarding addresses) of the desk: id, name, the address tickets arrive at and the from address. GET /emails.
No parameter schema on file.
A report as time-series data points (value, timestamp): tickets_count, replies_count or avg_first_response_time, optionally for one agent, team or label. Needs an admin token. GET /reports/{report}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report | string | yes | Which report. |
| user | integer | no | Only this agent (user id). |
| team | integer | no | Only this team (team id). |
| label | string | no | Only this label (name). |
| since | string | no | Start of the period (date, ISO date-time or Unix timestamp). |
WRITE: SENDS AN E-MAIL to the customer. Posts a public reply on ONE ticket; SupportBee e-mails it to the ticket's requester and to the cc/bcc addresses you list (at most 10 addresses in total). It cannot be recalled. The reply comes from the token's user. For a note only your team sees, use supportbee_add_comment. POST /tickets/{id}/replies.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
| text | string | yes | The reply text (plain text; blank lines separate paragraphs). |
| cc | array | no | Extra recipients in cc (cc + bcc together at most 10). |
| bcc | array | no | Extra recipients in bcc (cc + bcc together at most 10). |
WRITE: adds an internal comment to a ticket. Comments are visible to your agents only and are never e-mailed to the customer. POST /tickets/{id}/comments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
| text | string | yes | The comment text (plain text; blank lines separate paragraphs). |
WRITE: adds an existing label to a ticket (404 if the label does not exist; names come from supportbee_list_labels). Safe to repeat. POST /tickets/{id}/labels/{label}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
| label | string | yes | The label name, exactly as in supportbee_list_labels. |
WRITE: removes a label from a ticket (the label itself stays; 404 if the ticket does not have it). DELETE /tickets/{id}/labels/{label}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
| label | string | yes | The label name. |
WRITE: assigns a ticket to ONE agent (user_id) or ONE team (team_id), not both. A ticket that belongs to a team can only go to a member of that team; assigning to another team removes the user assignee. The customer is not e-mailed (SupportBee may notify the assigned agent). POST /tickets/{id}/user_assignment or /team_assignment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
| user_id | integer | no | The agent id (supportbee_list_users). |
| team_id | integer | no | The team id (supportbee_list_teams). |
WRITE: clears the user assignee or the team assignee of a ticket. DELETE /tickets/{id}/user_assignment or /team_assignment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
| assignee | string | yes | Which assignment to clear. |
WRITE: archives a ticket (archived=true, it leaves the open inbox) or moves it back (archived=false). Nothing is deleted or sent. POST/DELETE /tickets/{id}/archive.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
| archived | boolean | yes | true = archive, false = move back to the inbox. |
WRITE: marks a ticket as answered (answered=true) or unanswered (answered=false) without sending anything. POST/DELETE /tickets/{id}/answered.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_id | integer | yes | The SupportBee ticket id (the number in the ticket URL; from supportbee_list_tickets). |
| answered | boolean | yes | true = mark answered, false = mark unanswered. |
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 SupportBee MCP by usefulapi 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.0.0.
1.0.0
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 SupportBee MCP by usefulapi 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.