HappyFox MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.39.1Updated Nov 14, 2026

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

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableKnowledge & Memory Data & Analytics Business & Commerce

Server details

Identifier: io.usefulapi/happyfox
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 30, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to usefulapi.io, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.usefulapi%2Fhappyfox.svg)](https://sourceweft.com/mcp/io.usefulapi%2Fhappyfox?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Hosted HappyFox connector that lets an assistant triage tickets and contacts, run saved reports, export KB articles, and reply or add private notes.

What you can do: List, search and fetch tickets with full conversations, SLA breaches and attachment links
List and fetch contacts and contact groups, and create or edit contacts
List categories, staff, statuses, priorities and ticket/contact custom fields
List saved reports and pull report summaries and tabular ticket rows
Export external or internal knowledge-base articles
Create tickets, add agent replies or private notes, and update tags and custom fields
When to use it: Useful when a support team works in HappyFox and wants an assistant to answer questions about open tickets, priorities, contacts and reports, or to draft replies, notes and ticket updates without switching tools.
Requirements: Remote MCP endpoint over streamable HTTP; no local install. Sign-in is via OAuth, and the login page asks for the HappyFox help-desk subdomain, region, API key and auth code. Credentials are stored per user. A free plan allows 50 tool calls per month; paid plans raise the limit.

Before you install

Write tools create tickets, reply to contacts, add notes, change tags and custom fields, and create or edit contacts; the server asks for confirmation first. A reply emails the contact only when update_customer is true. Creating a contact with an existing email updates it and resets custom fields not passed. Paid plans are billed through a Stripe checkout link, and cancellation gives no refund for the current period.

Installation

In SourceWeft

Open HappyFox MCP by usefulapi in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Fhappyfox/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "happyfox-by-usefulapi": {
      "type": "http",
      "url": "https://happyfox.usefulapi.io/mcp"
    }
  }
}

README

HappyFox MCP by usefulapi

Use HappyFox from Claude, Cursor, or any MCP client — triage tickets, contacts and KB articles, run reports, and reply or add private notes. Hosted, no local install: connect with your own HappyFox credentials.

Live endpoint: https://happyfox.usefulapi.io/mcp · Homepage: https://usefulapi.io/happyfox

Connect

Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://happyfox.usefulapi.io/mcp.
Claude Code: claude mcp add --transport http happyfox https://happyfox.usefulapi.io/mcp, then run /mcp to log in.
VS Code: Add to VS Code.
Cursor and other clients: add the URL as a remote MCP server:

Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your HappyFox credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/happyfox/

On first connect you'll provide your HappyFox help-desk subdomain, region, API key and auth code (Manage → Integrations → API → Create API key). They're validated, stored per-user, and scoped to you — no keys in config files.

Tools

Tool	Type	What it does
`happyfox_list_tickets`	read	List or search tickets
`happyfox_get_ticket`	read	Get one ticket
`happyfox_list_contacts`	read	List or search contacts
`happyfox_get_contact`	read	Get one contact
`happyfox_list_contact_groups`	read	List contact groups
`happyfox_get_contact_group`	read	Get one contact group
`happyfox_list_categories`	read	List categories
`happyfox_list_staff`	read	List agents
`happyfox_list_statuses`	read	List statuses
`happyfox_list_priorities`	read	List priorities
`happyfox_list_ticket_custom_fields`	read	List ticket custom fields
`happyfox_list_contact_custom_fields`	read	List contact custom fields
`happyfox_list_reports`	read	List reports
`happyfox_get_report_summary`	read	Get a report summary
`happyfox_get_report_tabular_data`	read	Get a report's ticket rows
`happyfox_list_kb_articles`	read	Export knowledge-base articles
`happyfox_create_ticket`	write	Create a ticket
`happyfox_add_staff_reply`	write	Reply to a ticket as an agent
`happyfox_add_private_note`	write	Add a private note to a ticket
`happyfox_update_ticket_tags`	write	Add or remove ticket tags
`happyfox_update_ticket_custom_fields`	write	Edit a ticket's custom fields
`happyfox_create_contact`	write	Create a contact
`happyfox_update_contact`	write	Edit a contact
`happyfox_usage_status`	meta	Usage status (free-tier meter)
`happyfox_request_feature`	meta	Request a missing feature
`happyfox_upgrade`	meta	Upgrade to Pro or Pro+
`happyfox_cancel_subscription`	meta	Cancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

Each paid plan covers this server only. Ask your AI to run happyfox_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with happyfox_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with happyfox_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT © usefulapi. Not affiliated with or endorsed by HappyFox.

Source: servers/happyfox/README.md at commit f22f848

Tools

happyfox_list_tickets

List or search 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:"[email protected]"`, `unresponded:true`, `breached:true`, `duedate:overdue`, `created-after:"2026/01/31"`, `last-modified-on-or-after:"2026/09/01"`, `"Custom Field":"value"`. Separate several filters with a space. HappyFox: GET /api/1.1/json/tickets/.

Parametersqpagesizesortfieldsstatuscategoryminify_response

happyfox_get_ticket

Get one 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/<ticket_number>/.

Parametersticket_numberrequiredshow_cf_changes

happyfox_list_contacts

List or search 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.1/json/users/.

Parametersqpagesize

happyfox_get_contact

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

Parameterscontactrequired

happyfox_list_contact_groups

List contact groups

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

Takes no parameters.

happyfox_get_contact_group

Get one contact group

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

Parameterscontact_group_idrequired

happyfox_list_staff

List agents

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

Takes no parameters.

happyfox_list_statuses

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

Takes no parameters.

happyfox_list_priorities

List priorities

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

Takes no parameters.

happyfox_list_ticket_custom_fields

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

Takes no parameters.

happyfox_list_contact_custom_fields

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

Takes no parameters.

happyfox_list_reports

List reports

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

Takes no parameters.

happyfox_get_report_summary

Get a report summary

Summary counts for a saved report: ticket, completed, assigned, pending and unassigned counts. HappyFox: GET /api/1.1/json/report/<id>/.

Parametersreport_idrequired

happyfox_get_report_tabular_data

Get a report's ticket rows

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

Parameterspagesizereport_idrequired

happyfox_list_kb_articles

Export knowledge-base 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/.

Parametersinternal

happyfox_create_ticket

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

Parametersccbcchtmlnamerequiredtagstextemailrequiredphonesubjectrequiredassigneecategoryrequireddue_date+3 more

happyfox_add_staff_reply

Reply to a ticket as an agent

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

Parametersccbcchtmltagsstaffrequiredstatussubjectassigneedue_datepriorityplaintexttime_spent+4 more

happyfox_add_private_note

Add a private note to a ticket

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

Parametershtmltagsalertstaffrequiredstatusassigneedue_datepriorityplaintexttime_spentcustom_fieldsticket_numberrequired

happyfox_update_ticket_tags

Add or remove 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/.

Parametersaddremovestaff_idrequiredticket_numberrequired

happyfox_update_ticket_custom_fields

Edit a ticket's 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/.

Parametersstaffrequiredcustom_fieldsrequiredticket_numberrequired

happyfox_create_contact

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

Parametersnamerequiredemailrequiredphonescustom_fields

happyfox_update_contact

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

Parametersnameemailcontact_idrequiredcustom_fields

Version history

v1.39.1LatestNov 13, 2026
v1.38.0Nov 12, 2026
v1.37.3Nov 11, 2026
v1.36.5Nov 8, 2026
v1.36.4Nov 7, 2026
v1.35.3Nov 5, 2026
v1.35.2Nov 5, 2026
v1.35.1Nov 4, 2026
v1.35.0Nov 3, 2026
v1.34.1Nov 3, 2026
v1.33.0Nov 1, 2026
v1.31.0Oct 31, 2026
v1.30.0Oct 31, 2026
v1.29.2Oct 30, 2026
v1.29.0Oct 30, 2026
v1.24.0Oct 26, 2026
v1.21.3Oct 25, 2026
v1.21.0Oct 25, 2026
v1.20.0Oct 24, 2026
v1.17.0Oct 23, 2026
v1.16.4Oct 22, 2026
v1.16.3Oct 21, 2026
v1.11.1Oct 9, 2026
v1.10.0Oct 9, 2026
v1.0.0Sep 30, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts