Connect HappyFox to Claude Code

Let Claude draft replies, triage, and resolve tickets in HappyFox. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect HappyFox to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect HappyFox, you add a HappyFox MCP server: a small hosted service that exposes HappyFox's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own HappyFox account. No API keys pasted into config files.

claude mcp add --transport http happyfox https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in HappyFox once connected?

Full read-write HappyFox access lets Claude post a public reply or private note on a ticket, change status and priority, assign the right agent or team, apply tags and categories, and update custom fields once you approve. Triage and drafting happen inside the ticket rather than in a separate window.

Post a public reply or add a private internal note on a ticket
Change a ticket's status, priority, or category as you triage
Assign or reassign a ticket to an agent or team
Apply or remove tags and update custom fields
Find tickets matching a query and propose batched responses for approval

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same HappyFox access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the HappyFox API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when HappyFox changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build HappyFox connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same HappyFox connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own HappyFox account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on HappyFox's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to HappyFox?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the HappyFox account it signs in with. Revoking access is one click in HappyFox.

More on the HappyFox connector

HappyFox connector for claude.ai Gorgias + Claude Code Kustomer + Claude Code Zoho Desk + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us