Helpdesk
HappyFox MCP connector
The HappyFox connector lets Claude, ChatGPT, Cursor, or the Elaichi Agent post a reply on a HappyFox ticket for the person who signed in, with every reply recorded in an audit log.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
1 tool
How to connect
How to connect HappyFox to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect HappyFox once
-
Open Connections, choose Add connection, and pick HappyFox.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a HappyFox API key. One person generates a token in HappyFox and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect HappyFox to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect HappyFox to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect HappyFox to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect HappyFox to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with HappyFox through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Send the follow-up after a call
Tell the agent which HappyFox ticket you just discussed and what was agreed, and it posts the reply so the customer has it in writing before they hang up.
-
Support
Close the loop when a fix ships
Once engineering confirms the bug is gone, ask the agent to reply on the open HappyFox ticket letting the customer know and inviting them to check.
-
Customer Success
Answer a renewal question on the ticket
When an account manager already knows the answer, they can dictate it and have the reply land on the HappyFox ticket without opening the helpdesk themselves.
-
IT
Confirm a hardware request is done
After the laptop or license is handed over, post a short reply on the employee's HappyFox ticket so the request has a clear ending on record.
-
HR
Reply to a benefits or leave request
HR teams running an internal helpdesk on HappyFox can draft the answer in plain language and post it as a reply on the employee's ticket.
-
Facilities
Acknowledge a maintenance report
When someone reports a broken door or a cold meeting room, reply on the HappyFox ticket with what is being done and when, straight from the conversation you are already in.
Try asking
- “Summarize the tickets my team replied to this week.”
- “Draft a user reply for the top billing ticket.”
- “Which HappyFox contacts are still waiting on a reply?”
AI tools
HappyFox tools for your AI agents
1 tool is ready to call through Elaichi's MCP endpoint the moment you connect HappyFox, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting HappyFox gets you
6 screens from the product, each doing one job for your HappyFox account.
The agent
Ask about HappyFox tickets in plain language.
Three starter prompts pull answers from live HappyFox tickets and replies.
- tickets
- replies
- users
- contacts
Ask Elaichi to work across your apps.
Summarize the tickets my team replied to this week.
Draft a user reply for the top billing ticket.
Which HappyFox contacts are still waiting on a reply?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach HappyFox here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
1 HappyFox tool covers ticket replies.
Tool names, resources and methods are listed, so no custom code is written.
- Create a HappyFox user reply
ElaichiToolsToolboxes
Each support team gets its own toolbox.
Toolboxes scope HappyFox tools to the teams that answer those tickets.
- Support
- Escalations
- Customer Success
- Billing
ElaichiToolboxesShared connections
Teammates reply in HappyFox without a credential.
The table shows who connected each HappyFox account and which teams share it.
- Support EMEA
- Support APAC
- Billing Queue
- Escalations
ElaichiConnectionsAudit log
Every HappyFox reply is written down.
When, who, what happened, type and resource sit in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts and posts HappyFox replies.
Six steps fetch tickets, group them, draft a digest, then post after approval.
HappyFox digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch tickets
HappyFox
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
HappyFox
Queued
Collections and dashboards
HappyFox ticket numbers land on a schedule.
Four metrics, 14 days of tickets created and a per team breakdown, computed directly.
HappyFox health
Refreshed 4 minutes ago · every 15 minutes · from the tickets collection
Tickets
1,284 ↓ 12%
Replies
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tickets created
Last 14 days
By team
Share of activity
Support EMEA 34%
Support APAC 27%
Billing Queue 21%
Escalations 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect HappyFox to Claude?
First, connect HappyFox in Elaichi by pasting in a HappyFox API key from your helpdesk settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi as yourself, and HappyFox is ready.
Does HappyFox work with ChatGPT and Cursor as well as Claude?
Yes. Once HappyFox is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect HappyFox once and every client you use picks it up.
What can an AI agent actually do with my HappyFox data?
This HappyFox connector does one thing: it posts a reply on a HappyFox ticket. You tell the agent which ticket and what you want to say, it drafts the wording if you ask, and the reply appears on the ticket in HappyFox. It does not read, search, assign, or close tickets, so it is a way to get replies out faster rather than a full helpdesk assistant.
Does connecting HappyFox give the AI everything in my helpdesk?
No. Every reply is posted using the HappyFox access of the person who signed in, so the agent can only reply on tickets that person could reply on in HappyFox. Elaichi can narrow that further with restrictions, and it can never grant more than the person already has in HappyFox.
Can I stop an agent from deleting or changing things in HappyFox?
This HappyFox connector cannot delete or edit anything; its only action is posting a reply on a ticket. If you want to block even that for some people, restrictions in Elaichi apply per action, and a blocked action is never shown to Claude, ChatGPT, or Cursor at all, so no prompt can reach it.
What happens to a HappyFox connection when someone leaves?
When you offboard someone in Elaichi, their ability to post replies to HappyFox through any AI client ends at once. A HappyFox connection they shared with a team keeps working for everyone else. If you want HappyFox gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.
Put HappyFox in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.