io.usefulapi/happyfox
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
HappyFox MCP by usefulapi
Publisher-provided description
Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes.
Summary by lookupd
Triages HappyFox support tickets, contacts and knowledge base articles, runs saved reports, and adds replies or private notes.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http happyfox https://happyfox.usefulapi.io/mcp
Codex, remote (streamable-http)
codex mcp add happyfox --url https://happyfox.usefulapi.io/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"happyfox": {
"url": "https://happyfox.usefulapi.io/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (23 tools)
Publisher-provided text
happyfox_list_ticketsList tickets, newest activity first, with optional filters and HappyFox's search syntax. Paginated (page_info + data). Search `q` examples: `status:"New","In Prhappyfox_get_ticketFetch a ticket with its full conversation: status, priority, category, contact, assignee, custom fields, SLA breaches and every update (messages, private notes,happyfox_list_contactsList contacts (customers), paginated, or search them. Search `q` fields: name, email, phone (digits only, no +), updated_since, created_since — e.g. `name:adamhappyfox_get_contactFetch 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_groupsList contact groups (typically customer companies) with their tagged email domains. HappyFox: GET /api/1.1/json/contact_groups/.happyfox_get_contact_groupFetch a contact group and its member contacts. HappyFox: GET /api/1.1/json/contact_group/<id>/.happyfox_list_categoriesList ticket categories (queues) with their ids — needed to create a ticket or filter tickets. HappyFox: GET /api/1.1/json/categories/.happyfox_list_staffList 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/stahappyfox_list_statusesList 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_prioritiesList ticket priorities with ids — ids used to set a ticket's priority. HappyFox: GET /api/1.1/json/priorities/.happyfox_list_ticket_custom_fieldsList 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_custhappyfox_list_contact_custom_fieldsList 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_reportsList the saved reports (id, name, description) from the Reports module. HappyFox: GET /api/1.1/json/reports/.happyfox_get_report_summarySummary counts for a saved report: ticket, completed, assigned, pending and unassigned counts. HappyFox: GET /api/1.1/json/report/<id>/.happyfox_get_report_tabular_dataThe 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>/tahappyfox_list_kb_articlesExport the knowledge base: external (customer-facing) articles by default, or internal (agent-only) articles. HappyFox: GET /api/1.1/json/kb/articles/ or /kb/inhappyfox_create_ticketOpen 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`. Hahappyfox_add_staff_replyAdd 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 (HappyFoxhappyfox_add_private_noteAdd 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/happyfox_update_ticket_tagsAdd 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_fieldsSet 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_fieldhappyfox_create_contactCreate 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 phappyfox_update_contactEdit 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: P
Details
- Version: 1.37.3
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 361 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/happyfox/
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/io.usefulapi/happyfox)
- 62071 servers
- Last crawl: 2026-11-11T16:39:06.253Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp