HappyFox MCP by usefulapi is an MCP server with 23 tools an agent can call, among them happyfox_add_private_note, happyfox_add_staff_reply, happyfox_create_contact. It answers at https://happyfox.usefulapi.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 29 September 2026; the last check, on 15 November 2026, succeeded.
Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
happyfox_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/. Inputs: ticket_number, staff, plaintext, html, alert, status |
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 complet Inputs: ticket_number, staff, plaintext, html, update_customer, subject |
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. HappyF Inputs: name, email, phones, custom_fields |
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/. Inputs: name, email, phone, subject, text, html |
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>/. Inputs: contact |
happyfox_get_contact_group | Fetch a contact group and its member contacts. HappyFox: GET /api/1.1/json/contact_group/<id>/. Inputs: contact_group_id |
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>/. Inputs: 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/. Inputs: report_id, page, size |
happyfox_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 /ap Inputs: ticket_number, show_cf_changes |
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_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/. |
happyfox_list_contact_groups | List contact groups (typically customer companies) with their tagged email domains. HappyFox: GET /api/1.1/json/contact_groups/. |
happyfox_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:[email protected]` (space-separated, all must match). HappyFox: GET /api/1. Inputs: q, page, size |
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/. Inputs: internal |
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_reports | List the saved reports (id, name, description) from the Reports module. HappyFox: GET /api/1.1/json/reports/. |
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_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_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@ex Inputs: q, status, category, sort, fields, minify_response |
happyfox_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>/. Inputs: contact_id, name, email, custom_fields |
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/. Inputs: ticket_number, staff, custom_fields |
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/. Inputs: ticket_number, staff_id, add, remove |
Every block below points at https://happyfox.usefulapi.io/mcp. Pick your client and copy.
claude mcp add --transport http happyfox-mcp-by-usefulapi https://happyfox.usefulapi.io/mcp
{
"mcpServers": {
"happyfox-mcp-by-usefulapi": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://happyfox.usefulapi.io/mcp"]
}
}
}{
"mcpServers": {
"happyfox-mcp-by-usefulapi": {
"url": "https://happyfox.usefulapi.io/mcp"
}
}
}{
"servers": {
"happyfox-mcp-by-usefulapi": {
"type": "http",
"url": "https://happyfox.usefulapi.io/mcp"
}
}
}{
"context_servers": {
"happyfox-mcp-by-usefulapi": {
"url": "https://happyfox.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"happyfox-mcp-by-usefulapi": {
"serverUrl": "https://happyfox.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"happyfox-mcp-by-usefulapi": {
"url": "https://happyfox.usefulapi.io/mcp"
}
}
}name: HappyFox MCP by usefulapi
version: 0.0.1
schema: v1
mcpServers:
- name: HappyFox MCP by usefulapi
type: streamable-http
url: https://happyfox.usefulapi.io/mcp{
"mcpServers": {
"happyfox-mcp-by-usefulapi": {
"httpUrl": "https://happyfox.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"happyfox-mcp-by-usefulapi": {
"type": "http",
"url": "https://happyfox.usefulapi.io/mcp"
}
}
}{
"mcpServers": {
"happyfox-mcp-by-usefulapi": {
"url": "https://happyfox.usefulapi.io/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fhappyfox.usefulapi.io%2Fmcp&type=streamable_http&id=happyfox-mcp-by-usefulapi&name=HappyFox%20MCP%20by%20usefulapi
It answered our last check on 15 November 2026 in 1035 ms. Over 4 checks since 29 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by usefulapi.io and served from happyfox.usefulapi.io, the vendor's own domain: https://happyfox.usefulapi.io/mcp.
23, as returned by the server's own tools/list on 18 November 2026: happyfox_add_private_note, happyfox_add_staff_reply, happyfox_create_contact, happyfox_create_ticket, happyfox_get_contact, happyfox_get_contact_group, happyfox_get_report_summary, happyfox_get_report_tabular_data, and 15 more.
It answered our last check on 15 November 2026 in 1035 ms. Over 4 checks since 29 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://happyfox.usefulapi.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.usefulapi. Endpoint host: happyfox.usefulapi.io. ARD identifier: urn:air:io.usefulapi:mcp:happyfox.
First indexed 29 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.