What can HappyFox MCP by usefulapi do?

It exposes 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, happyfox_list_statuses, happyfox_list_priorities, happyfox_list_ticket_custom_fields, happyfox_list_contact_custom_fields.

Is HappyFox MCP by usefulapi safe and reliable?

Trust score 82/100 (grade B), based on live reachability, verified publisher, maintenance, adoption, transparency and tool quality. See our methodology.

Servers / Productivity

HappyFox MCP by usefulapi

io.usefulapi/happyfox

Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes.

Compare Website ↗Source ↗

Yes, your AI can use this right now.Answered a live MCP handshake in 222 ms with no sign-in needed and exposes 23 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://happyfox.usefulapi.io/mcp

Settings → Apps & Connectors → Advanced → Developer mode
Create connector with URL: https://happyfox.usefulapi.io/mcp

{
  "mcpServers": {
    "happyfox": {
      "url": "https://happyfox.usefulapi.io/mcp"
    }
  }
}

claude mcp add --transport http happyfox https://happyfox.usefulapi.io/mcp

{
  "servers": {
    "happyfox": {
      "type": "http",
      "url": "https://happyfox.usefulapi.io/mcp"
    }
  }
}

23 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.

happyfox_list_ticketsread-only

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

happyfox_get_ticketread-only

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>/.

happyfox_list_contactsread-only

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/.

happyfox_get_contactread-only

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_groupsread-only

List contact groups (typically customer companies) with their tagged email domains. HappyFox: GET /api/1.1/json/contact_groups/.

happyfox_get_contact_groupread-only

Fetch a contact group and its member contacts. HappyFox: GET /api/1.1/json/contact_group/<id>/.

happyfox_list_categoriesread-only

List ticket categories (queues) with their ids — needed to create a ticket or filter tickets. HappyFox: GET /api/1.1/json/categories/.

happyfox_list_staffread-only

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_statusesread-only

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_prioritiesread-only

List ticket priorities with ids — ids used to set a ticket's priority. HappyFox: GET /api/1.1/json/priorities/.

happyfox_list_ticket_custom_fieldsread-only

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_fieldsread-only

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_reportsread-only

List the saved reports (id, name, description) from the Reports module. HappyFox: GET /api/1.1/json/reports/.

happyfox_get_report_summaryread-only

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_dataread-only

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_articlesread-only

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_ticketcan modify

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_replycan modify

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/.

happyfox_add_private_notecan modify

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_tagscan modify

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_fieldscan modify

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_contactcan modify

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/.

happyfox_update_contactcan modify

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>/.

Alternatives in Productivity

Compare →

HappyFox MCP by usefulapi

Connect it

23 tools, verified live

Alternatives in Productivity

ARArB

MUMundaneB

Local MCPB

Fieldwire MCP by usefulapiB

Homerun MCP by usefulapiB

AddEvent MCP by usefulapiB