HappyFox MCP by usefulapi
Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: triage support tickets.Similar tools
Listed for the same task: triage support ticketsReviews
No review yet. Used HappyFox MCP by usefulapi? Be the first to help others choose.What it does
HappyFox MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: ticket triage. That makes it a candidate for tasks such as triage support tickets or automate customer support.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 9h ago (live check)Hosted endpoint
https://happyfox.usefulapi.io/mcpstreamable-http
In Claude Code: claude mcp add --transport http happyfox https://happyfox.usefulapi.io/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"happyfox": {
"url": "https://happyfox.usefulapi.io/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 9h agoONLINE HappyFox MCP by usefulapi answered an MCP connection on 15 Nov 2026 and introduced itself as happyfox-mcp 1.39.2 (MCP protocol 2025-06-18).
23 tools offered to AI assistants
happyfox_list_tickets· 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@exhappyfox_get_ticket· 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 /aphappyfox_list_contacts· 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.happyfox_get_contact· 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>/.happyfox_list_contact_groups· List contact groups (typically customer companies) with their tagged email domains. HappyFox: GET /api/1.1/json/contact_groups/.happyfox_get_contact_group· Fetch a contact group and its member contacts. HappyFox: GET /api/1.1/json/contact_group/<id>/.happyfox_list_categories· List ticket categories (queues) with their ids — needed to create a ticket or filter tickets. HappyFox: GET /api/1.1/json/categories/.happyfox_list_staff· 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/.happyfox_list_statuses· List ticket statuses with ids and behaviour (pending / completed) — ids used to change a ticket's status. HappyFox: GET /api/1.1/json/statuses/.happyfox_list_priorities· List ticket priorities with ids — ids used to set a ticket's priority. HappyFox: GET /api/1.1/json/priorities/.happyfox_list_ticket_custom_fields· 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/.happyfox_list_contact_custom_fields· 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/.
Show 11 more
happyfox_list_reports· List the saved reports (id, name, description) from the Reports module. HappyFox: GET /api/1.1/json/reports/.happyfox_get_report_summary· Summary counts for a saved report: ticket, completed, assigned, pending and unassigned counts. HappyFox: GET /api/1.1/json/report/<id>/.happyfox_get_report_tabular_data· 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/.happyfox_list_kb_articles· 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/.happyfox_create_ticket· 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/.happyfox_add_staff_reply· 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 complethappyfox_add_private_note· 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/.happyfox_update_ticket_tags· Add and/or remove tags on a ticket without touching anything else. HappyFox: POST /api/1.1/json/ticket/<ticket_number>/update_tags/.happyfox_update_ticket_custom_fields· 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/.happyfox_create_contact· 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. HappyFhappyfox_update_contact· 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>/.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 1.39.2 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Hosted endpoint | https://happyfox.usefulapi.io/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://usefulapi.io/happyfox/ | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/m190/usefulapi-mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
- VERSION14 Nov 20261.39.1 → 1.39.2
- VERSION13 Nov 20261.39.0 → 1.39.1
- VERSION13 Nov 20261.38.0 → 1.39.0
- VERSION11 Nov 20261.37.3 → 1.38.0
- VERSION11 Nov 20261.37.2 → 1.37.3
- VERSION10 Nov 20261.37.1 → 1.37.2
- VERSION10 Nov 20261.37.0 → 1.37.1
- VERSION10 Nov 20261.36.5 → 1.37.0
- VERSION07 Nov 20261.36.4 → 1.36.5
- VERSION07 Nov 20261.36.3 → 1.36.4
- VERSION07 Nov 20261.36.2 → 1.36.3
- VERSION06 Nov 20261.36.1 → 1.36.2
- VERSION06 Nov 20261.35.4 → 1.36.1
- VERSION06 Nov 20261.35.3 → 1.35.4
- VERSION05 Nov 20261.35.2 → 1.35.3
- VERSION05 Nov 20261.35.1 → 1.35.2
- VERSION03 Nov 20261.35.0 → 1.35.1
- VERSION03 Nov 20261.34.1 → 1.35.0
- VERSION03 Nov 20261.34.0 → 1.34.1
- VERSION02 Nov 20261.33.0 → 1.34.0
- VERSION31 Oct 20261.32.0 → 1.33.0
- VERSION31 Oct 20261.31.0 → 1.32.0
- VERSION31 Oct 20261.30.0 → 1.31.0
- VERSION31 Oct 20261.29.2 → 1.30.0
- VERSION30 Oct 20261.29.1 → 1.29.2
- VERSION30 Oct 20261.29.0 → 1.29.1
- VERSION29 Oct 20261.28.0 → 1.29.0
- VERSION29 Oct 20261.27.0 → 1.28.0
- VERSION28 Oct 20261.26.0 → 1.27.0
- VERSION28 Oct 20261.25.0 → 1.26.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is HappyFox MCP by usefulapi still online?
Free alerts · no account▲ 0Do you run HappyFox MCP by usefulapi? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about HappyFox MCP by usefulapi
How do I connect HappyFox MCP by usefulapi?
Use the hosted endpoint https://happyfox.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does HappyFox MCP by usefulapi offer?
When Electra Index connected on 15 Nov 2026, it listed 23 tools: happyfox_list_tickets, happyfox_get_ticket, happyfox_list_contacts, happyfox_get_contact, happyfox_list_contact_groups, happyfox_get_contact_group, happyfox_list_categories, happyfox_list_staff and more. The full list is in "Live check" above.
Is HappyFox MCP by usefulapi online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 9h ago.
What can I use HappyFox MCP by usefulapi for?
Based on its description, it is most relevant to: triage support tickets, automate customer support.