HappyFox MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Docs, sheets & office work

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://happyfox.usefulapi.io/mcp

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

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

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

https://happyfox.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• 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@example.com"`, `unresponded:true`, `breach

• 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 /api/1.1/json/ticket/ /.

• 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:adam@example.com` (space-separated, all must match). HappyFox: GET /api/1.1/json/users/.

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

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

• 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- . 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- . HappyFox: GET /api/1.1/json/user_custom_fields/.

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

• 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/ /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 completed status may require the category's com

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

• happyfox_update_ticket_custom_fields

  Set ticket custom-field values (t-cf- , ids from happyfox_list_ticket_custom_fields). HappyFox: POST /api/1.1/json/ticket/ /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. HappyFox: POST /api/1.1/json/users/.

• happyfox_update_contact

  Edit an existing contact's name, email or contact custom fields (c-cf- ). Phone numbers are edited via happyfox_create_contact with the phone id. HappyFox: POST /api/1.1/json/user/ /.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 37 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 23 tool descriptions and found no hidden instructions to the AI

Compared with others in Docs, sheets & office worki

• More stars than 0% of the other 2170 servers in this category
• Published to the registry more recently than 96% of the other 2170 servers in this category
• Basic checks equal to or better than 100% of the other 2170 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{