HappyFox MCP server
HappyFox in any MCP client, through Memtro: HappyFox does not publish this server. Memtro's HappyFox connector reads HappyFox through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
HappyFox help desk: tickets by status, category, search, contact or date with their conversation and notes, contacts and contact groups, and the categories, statuses, priorities, agents and custom fields their ids refer to; when you ask, can create tickets, reply as an agent (emailing the contact only when told to), change status, priority, assignee, due date, tags or custom fields, add private notes, subscribe agents, move, forward or delete tickets, and add or edit contacts.
Reads
happyfox_list_ticketsList HappyFox tickets: subject, status, priority, category, assignee, contact, created and last-modified times, due date, tags.happyfox_get_ticketOne HappyFox ticket by its number, with its custom fields and its latest updates: replies, private notes and status, priority or assignee changes…happyfox_list_contactsHappyFox contacts: name, ticket counts, contact groups.happyfox_lookupsThe ids HappyFox writes need: categories, statuses (with whether they are pending or completed), priorities, staff (agents…
Acts, when you ask
These change something in HappyFox. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
happyfox_create_ticketCreates a HappyFox ticket in a public category for a contact (an existing contact id, or a new contact's name and email).happyfox_replyAdds an agent reply to a HappyFox ticket as the agent named in staff_id.happyfox_update_ticketChanges a HappyFox ticket's status, priority, assignee or due date as the agent named in staff_id, with no message and no email to the contact.happyfox_add_noteAdds a private note to a HappyFox ticket as the agent named in staff_id; the contact never sees it.happyfox_set_custom_fieldsSets ticket custom field values on a HappyFox ticket as the agent named in staff_id; nobody is emailed.happyfox_update_tagsAdds and/or removes tags on a HappyFox ticket, shown as done by the agent in staff_id; nobody is emailed.happyfox_subscribe_agentsSubscribes agents to a HappyFox ticket so they are notified of its updates; staff_id is the agent making the change and also subscribed.happyfox_unsubscribe_agentUnsubscribes one agent (staff_id) from a HappyFox ticket, so they stop receiving its notifications.happyfox_move_ticketMoves a HappyFox ticket to another category as the agent in staff_id, optionally assigning it and leaving a note…happyfox_forward_ticketEmails a HappyFox ticket's conversation to the outside addresses given, as the agent in staff_id, with the subject and message given.happyfox_delete_ticketDeletes a HappyFox ticket, recorded as done by the agent in staff_id; HappyFox documents no way to restore it through the API.happyfox_create_contactAdds a contact to HappyFox with a name and email; nobody is emailed by this call.happyfox_update_contactChanges a HappyFox contact's name or email address; only the fields passed change.
Connect it
First connect HappyFox on Dashboard → Connections, then add Memtro to your client once. The HappyFox tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared HappyFox connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which high-priority tickets are unassigned?
- › Which tickets have had no response yet?
- › What is the latest update on ticket 4410?
- › Which tickets has Northwind raised this month?
- › Add a private note to ticket 4410 that the fix ships on Friday.
Questions
- Is this an official HappyFox MCP server?
- No. It is Memtro's MCP server with Memtro's HappyFox connector behind it: the connector reads HappyFox through its API with the credentials you connect on Dashboard → Connections, and HappyFox publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in HappyFox?
- Only when you ask, and only what it has been granted: create a ticket (HappyFox emails the contact as usual); reply to a ticket as an agent, emailing the contact only when told to; change a ticket's status, priority, assignee or due date; add a private note to a ticket; set a ticket's custom fields; add or remove tags on a ticket; subscribe agents to a ticket; unsubscribe an agent from a ticket; move a ticket to another category; forward a ticket to an outside email address; delete a ticket; add a contact; edit a contact's name or email. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.