MCP server for interacting with your LINE Official Account
Nothing to run from here
Happyfox 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.
23
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http happyfox-mcp https://happyfox.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# happyfox_list_tickets, happyfox_get_ticket, happyfox_list_contacts and 20 more
Happyfox 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 happyfox-mcp https://happyfox.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
23 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, newest activity first, with optional filters and HappyFox's search syntax. Paginated (page_info + data). Search q examples: status:"New","In Progress", priority:"High", assignee:none, tag:"billing", contact:"jane@example.com", unresponded:true, breached:true, duedate:overdue, created-after:"2026/01/31", last-modified-on-or-after:"2026/09/01", `"Custom Field":"va
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | HappyFox search/filter string (see description). |
| status | string | no | _all (default), _pending (every pending-behaviour status), or a status id from happyfox_list_statuses. |
| category | integer | no | Only tickets in this category id (happyfox_list_categories). |
| sort | string | no | Sort key, e.g. created (newest first), createa, updated, due, priorityd. |
| fields | string | no | Comma-separated top-level fields to return, e.g. id,display_id,subject,status — keeps responses small. |
| minify_response | boolean | no | If true, return only ticket ids. |
| page | integer | no | Page number, starting at 1. |
| size | integer | no | Results per page, 1-50 (HappyFox default 10). |
Fetch a ticket with its full conversation: status, priority, category, contact, assignee, custom fields, SLA breaches and every update (messages, private notes, property changes, attachment links that expire in 5 minutes). HappyFox: GET /api/1.1/json/ticket/<ticket_number>/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_number | integer | yes | The ticket NUMBER (the id field, e.g. 3 for #DC00000003) — not the prefixed display id. |
| show_cf_changes | boolean | no | Include the history of custom-field changes in the updates. |
List contacts (customers), paginated, or search them. Search q fields: name, email, phone (digits only, no +), updated_since, created_since — e.g. name:adam email:adam@example.com (space-separated, all must match). HappyFox: GET /api/1.1/json/users/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Search string, field:value pairs separated by spaces. |
| page | integer | no | Page number, starting at 1. |
| size | integer | no | Results per page, 1-50 (HappyFox default 10). |
Fetch a contact by id or by email address — phones, contact groups, ticket counts and custom fields. HappyFox: GET /api/1.1/json/user/<id or email>/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact | string | yes | The contact's numeric id (e.g. "33") or email address. |
List contact groups (typically customer companies) with their tagged email domains. HappyFox: GET /api/1.1/json/contact_groups/.
No parameter schema on file.
Fetch a contact group and its member contacts. HappyFox: GET /api/1.1/json/contact_group/<id>/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_group_id | integer | yes | The contact group id. |
List ticket categories (queues) with their ids — needed to create a ticket or filter tickets. HappyFox: GET /api/1.1/json/categories/.
No parameter schema on file.
List agents (staff) with their ids, roles, categories and active flag — the staff id every reply/note needs, and assignee ids. HappyFox: GET /api/1.1/json/staff/.
No parameter schema on file.
List ticket statuses with ids and behaviour (pending / completed) — ids used to change a ticket's status. HappyFox: GET /api/1.1/json/statuses/.
No parameter schema on file.
List ticket priorities with ids — ids used to set a ticket's priority. HappyFox: GET /api/1.1/json/priorities/.
No parameter schema on file.
List ticket custom fields: id, type, choices (with choice ids), required flags and categories. Use the ids as t-cf-<id>. HappyFox: GET /api/1.1/json/ticket_custom_fields/.
No parameter schema on file.
List contact custom fields: id, type, choices and required flag. Use the ids as c-cf-<id>. HappyFox: GET /api/1.1/json/user_custom_fields/.
No parameter schema on file.
List the saved reports (id, name, description) from the Reports module. HappyFox: GET /api/1.1/json/reports/.
No parameter schema on file.
Summary counts for a saved report: ticket, completed, assigned, pending and unassigned counts. HappyFox: GET /api/1.1/json/report/<id>/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | integer | yes | The report (from happyfox_list_reports) id. |
The tabular view of a saved report — one row per ticket (display_id, subject, status, assignee, due date), paginated. HappyFox: GET /api/1.1/json/report/<id>/tabulardata/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | integer | yes | The report (from happyfox_list_reports) id. |
| page | integer | no | Page number, starting at 1. |
| size | integer | no | Results per page, 1-50 (HappyFox default 10). |
Export the knowledge base: external (customer-facing) articles by default, or internal (agent-only) articles. HappyFox: GET /api/1.1/json/kb/articles/ or /kb/internal-articles/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| internal | boolean | no | true = internal articles; false/omitted = external articles. |
Open a new ticket on behalf of a contact (created if the email is new). Needs a category id (a public category), a subject and a message in text or html. HappyFox: POST /api/1.1/json/tickets/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Contact name. |
| string | yes | Contact email address. | |
| phone | string | no | Contact phone number. |
| subject | string | yes | Ticket subject. |
| text | string | no | Message in plain text (text or html is required). |
| html | string | no | Message in HTML (text or html is required). |
| category | integer | yes | The category (happyfox_list_categories; must be public) id. |
| priority | integer | no | Priority id (happyfox_list_priorities); defaults to the default priority. |
| assignee | no | Agent id to assign the ticket to (from happyfox_list_staff); null to unassign. | |
| tags | string | no | Tags, as a comma-separated string. |
| cc | string | no | CC email addresses, as a comma-separated string. |
| bcc | string | no | BCC email addresses, as a comma-separated string. |
| due_date | string | no | Due date, yyyy-mm-dd or dd/mm/yyyy. |
| visible_only_staff | boolean | no | true = private ticket, visible to staff only. |
| custom_fields | object | no | Custom field values keyed "t-cf-<id>" / "c-cf-<id>". Ticket (t-cf-) and contact (c-cf-) fields; required ones must be present. Values: text = string, number = number, dropdown = choice id, multiple ch |
Add an agent reply to a ticket and/or change its status, priority, assignee, due date or tags. The contact is emailed ONLY if update_customer is true (HappyFox default: false). With no message it just updates properties. Moving to a completed status may require the category's compulsory custom fields. HappyFox: POST /api/1.1/json/ticket/<ticket_number>/staff_update/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_number | integer | yes | The ticket NUMBER (the id field, e.g. 3 for #DC00000003) — not the prefixed display id. |
| staff | integer | yes | The agent making the reply (happyfox_list_staff) id. |
| plaintext | string | no | Reply in plain text. |
| html | string | no | Reply in HTML. |
| update_customer | boolean | no | true = send the reply to the contact by email. Default false. |
| subject | string | no | Override the subject of the email sent to the contact. |
| cc | string | no | CC email addresses, as a comma-separated string. |
| bcc | string | no | BCC email addresses, as a comma-separated string. |
| send_survey | boolean | no | true = send the satisfaction survey. |
| status | integer | no | New status id (happyfox_list_statuses). |
| priority | integer | no | New priority id (happyfox_list_priorities). |
| assignee | no | Agent id to assign the ticket to (from happyfox_list_staff); null to unassign. | |
| time_spent | integer | no | Minutes to add to the ticket's time spent (some categories require it). |
| due_date | string | no | Due date, yyyy-mm-dd or dd/mm/yyyy. |
| tags | string | no | Tags to set, as a comma-separated string. |
| custom_fields | object | no | Custom field values keyed "t-cf-<id>". Ticket fields (ids from happyfox_list_ticket_custom_fields); compulsory-on-completion fields are required when closing. Values: text = string, number = number, d |
Add an internal note (never sent to the contact), optionally alerting agents and changing status, priority, assignee, due date or tags. HappyFox: POST /api/1.1/json/ticket/<ticket_number>/staff_pvtnote/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_number | integer | yes | The ticket NUMBER (the id field, e.g. 3 for #DC00000003) — not the prefixed display id. |
| staff | integer | yes | The agent adding the note (happyfox_list_staff) id. |
| plaintext | string | no | Note in plain text. |
| html | string | no | Note in HTML. |
| alert | string | no | Send a private alert: s = all subscribers, c = all agents in the ticket's category, or an agent id. |
| status | integer | no | New status id (happyfox_list_statuses). |
| priority | integer | no | New priority id (happyfox_list_priorities). |
| assignee | no | Agent id to assign the ticket to (from happyfox_list_staff); null to unassign. | |
| time_spent | integer | no | Minutes to add to the ticket's time spent (some categories require it). |
| due_date | string | no | Due date, yyyy-mm-dd or dd/mm/yyyy. |
| tags | string | no | Tags to set, as a comma-separated string. |
| custom_fields | object | no | Custom field values keyed "t-cf-<id>". Ticket fields (ids from happyfox_list_ticket_custom_fields); compulsory-on-completion fields are required when closing. Values: text = string, number = number, d |
Add and/or remove tags on a ticket without touching anything else. HappyFox: POST /api/1.1/json/ticket/<ticket_number>/update_tags/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_number | integer | yes | The ticket NUMBER (the id field, e.g. 3 for #DC00000003) — not the prefixed display id. |
| staff_id | integer | yes | The agent making the change (shown in the ticket history) id. |
| add | string | no | Tags to add, as a comma-separated string. |
| remove | string | no | Tags to remove, as a comma-separated string. |
Set ticket custom-field values (t-cf-<id>, ids from happyfox_list_ticket_custom_fields). HappyFox: POST /api/1.1/json/ticket/<ticket_number>/update_custom_fields/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticket_number | integer | yes | The ticket NUMBER (the id field, e.g. 3 for #DC00000003) — not the prefixed display id. |
| staff | integer | yes | The agent making the change id. |
| custom_fields | object | yes | Custom field values keyed "t-cf-<id>". Ticket fields only. Values: text = string, number = number, dropdown = choice id, multiple choice = array of choice ids, date = yyyy-mm-dd. |
Create a contact. HappyFox treats this as create-or-edit keyed on email: if the email already exists that contact is updated, and any contact custom field NOT passed is reset — use happyfox_update_contact to edit an existing contact. HappyFox: POST /api/1.1/json/users/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Contact name. |
| string | yes | Contact email address. | |
| phones | array | no | Phone numbers. |
| custom_fields | object | no | Custom field values keyed "c-cf-<id>". Contact fields (happyfox_list_contact_custom_fields); required ones must be present. Values: text = string, number = number, dropdown = choice id, multiple choic |
Edit an existing contact's name, email or contact custom fields (c-cf-<id>). Phone numbers are edited via happyfox_create_contact with the phone id. HappyFox: POST /api/1.1/json/user/<id>/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contact_id | integer | yes | The contact id. |
| name | string | no | New name. |
| string | no | New email address. | |
| custom_fields | object | no | Custom field values keyed "c-cf-<id>". Contact fields. Values: text = string, number = number, dropdown = choice id, multiple choice = array of choice ids, date = yyyy-mm-dd. |
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 Happyfox 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 Happyfox 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.