Connect-MCP

HappyFox MCP by usefulapi

io.usefulapi/happyfox · v1.11.1

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

MCPremoteno credentialsEmailKnowledge & docsCRM & sales

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 23 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 88/100

What it does: 23 tools · 16 read, 7 write (incl. delete/pay) · Email, Knowledge & docs, CRM & sales

Test call happyfox_list_tickets: needs a key: HTTP 401 (995 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://happyfox.usefulapi.io/mcp

Tools

23 tools listed at last check
  • 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:"[email protected]"`, `unresponded:true`, `breached:true`, `duedate:o
  • 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/<ticket_number>/.
  • 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.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/<id or email>/.
  • 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/<id>/.
  • 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-<id>. 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-<id>. 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/<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/.
  • 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 compulsory custom field
  • 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/.
  • 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/.
  • 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/.
  • 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-<id>). Phone numbers are edited via happyfox_create_contact with the phone id. HappyFox: POST /api/1.1/json/user/<id>/.

Badge

Connect-MCP badge for io.usefulapi/happyfox

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.usefulapi/happyfox.svg)](https://clawy.uk/mcp/s/io.usefulapi/happyfox)

Repository · Website