HappyFox MCP connector
The HappyFox connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- Connects with an API key
- Free 14-day trial
- No credit card
Claude
Elaichi connected
Summarize the tickets my team replied to this week.
Working in HappyFox with Elaichi
-
Create a HappyFox user reply
Governance
/
Audit log
Last 24 hours
Claude · 9:41 AM
Done
ChatGPT · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect HappyFox to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
HappyFox MCP connector for 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.
HappyFox MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
HappyFox MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
HappyFox MCP connector for 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.
HappyFox MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with HappyFox through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in HappyFox is logged.
-
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?”
What connecting HappyFox gets you
6 screens from Elaichi, each doing one job for your HappyFox account.
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, Cursor or Microsoft Copilot
The agent
Ask about HappyFox tickets in plain language.
Three starter prompts pull answers from live HappyFox tickets and replies.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach HappyFox here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiToolsTool catalog
1 HappyFox tool covers ticket replies.
Tool names, resources and methods are listed, so no custom code is written.
ElaichiToolboxesToolboxes
Each support team gets its own toolbox.
Toolboxes scope HappyFox tools to the teams that answer those tickets.
ElaichiConnectionsShared connections
Teammates reply in HappyFox without a credential.
The table shows who connected each HappyFox account and which teams share it.
ElaichiAudit logAudit log
Every HappyFox reply is written down.
When, who, what happened, type and resource sit in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
HappyFox digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
HappyFox
Queued
Automations
A schedule drafts and posts HappyFox replies.
Six steps fetch tickets, group them, draft a digest, then post after approval.
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%
Collections and dashboards
HappyFox ticket numbers land on a schedule.
Four metrics, 14 days of tickets created and a per team breakdown, computed directly.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for HappyFox
All three can connect HappyFox to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over HappyFox tools | Allow or restrict single HappyFox tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per HappyFox call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restrict even that for some people, restrictions in Elaichi apply per action, and a restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot, and every other client together.
Does the HappyFox MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. HappyFox is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for HappyFox?
Yes. Both let Claude, ChatGPT or Cursor use HappyFox. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every HappyFox call.
How is Elaichi different from Composio for HappyFox?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to HappyFox: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put HappyFox in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot