# 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. Source: https://elaichi.ai/connectors/happyfox/ ## Facts | | | | --- | --- | | Application | HappyFox | | Category | Helpdesk | | AI tools | 1 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once HappyFox is connected - 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? ## Connect HappyFox in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick HappyFox. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which HappyFox tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect HappyFox to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect HappyFox to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a HappyFox tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with HappyFox through Elaichi ### Send the follow-up after a call Support. 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. ### Close the loop when a fix ships Support. 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. ### Answer a renewal question on the ticket Customer Success. 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. ### Confirm a hardware request is done IT. 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. ### Reply to a benefits or leave request HR. 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. ### Acknowledge a maintenance report Facilities. 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. ## 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 my team share one HappyFox connection? Yes. One person connects HappyFox in Elaichi with the API key and shares the connection with a team, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so every reply posted to HappyFox is logged under the name of the person who asked for it. ### 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. ## All 1 HappyFox tools Every tool below is callable through https://api.elaichi.ai/mcp once HappyFox is connected, subject to the toolbox it is in and the restrictions on the caller. - **Create a HappyFox user reply** (Create). Add a reply by a contact (called user on HappyFox) on a ticket. Requires the ticket_id.