HappyFox logo happyfox.com

Live

HappyFox API and MCP server

The HappyFox API needs your own code and a lookup of integer IDs for every queue, status and agent. Sign in to HappyFox once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with HappyFox.

HappyFox has no API for this. So we run one for you.

HappyFox's own API, a GitHub MCP server and Cotlet compared
What you need HappyFox's APIGitHub MCP serverCotlet
Replies, notes, canned actions No Partly Yes, 12 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when HappyFox changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 20, 2026. Sources: HappyFox Support: API Reference, Tickets API Endpoints · HappyFox Support: How to create an API Key and Auth Code · HappyFox Support: Enabling API in your HappyFox account · Zapier: HappyFox integrations

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to HappyFox in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect HappyFox to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 12 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. HappyFox and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
    Codex
    # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/happyfox with its own method and path, such as PATCH /api/v1/happyfox/tickets/{ticket_id}, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the HappyFox API and MCP server do?

12 tools on your own HappyFox account. Agents call them as operations of the MCP tools happyfox_read and happyfox_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
HappyFox tools in Cotlet's MCP server and REST API
Tool What it does Access
search_tickets Tickets in a queue or matching a text search, with status, priority, category and assignee. read
get_ticket One ticket with its fields, tags and every update, staff replies, contact messages and private notes. read
list_queues Ticket queues you can open: the ready-made ones and the ones your team set up. read
list_categories Ticket categories with ID and name. read
list_statuses Ticket statuses with ID, name and behaviour, pending or completed. read
list_priorities Ticket priorities with ID and name. read
list_agents Agents who can be assigned tickets, with ID, name and role. read
list_canned_actions Canned actions with ID, name and the categories they are defined for. read
reply_to_ticket Send a reply to the contact and optionally set the status in the same call. writeasks first
add_private_note Add a note only your team can see, and optionally alert subscribers or agents. writeasks first
update_ticket Change status, priority, assignee or tags of one ticket. writeasks first
apply_canned_action Apply a canned action to a ticket as a reply or a private note and submit it. writeasks first

Scroll the table for all 12 tools.

Ask in plain words. Your agent does the rest.

All HappyFox use cases

Is it safe to connect HappyFox?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the HappyFox API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while HappyFox is enabled for agents, so 20 calls a day come to 550 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 25 credits each
Credits Price, one time Calls at 25 credits Per 1,000 credits
5,000 $29 200 $5.80
15,000 $79 600 $5.27
32,000 $149 1,280 $4.66
60,000 $249 2,400 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does HappyFox have an API?

HappyFox has a full REST API (version 1.1) for tickets, contacts and assets, but no official MCP server for working tickets (checked 20 Oct 2026). The API uses an API key and auth code from an app an admin enables, and it takes status, priority, assignee and custom fields as integer IDs.

How do I get access?

Sign up free, open HappyFox under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 12 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to HappyFox yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so HappyFox sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: reply_to_ticket, add_private_note, update_ticket, apply_canned_action wait for your OK by default. You can switch that off per tool for scheduled runs.

Do I need to enable the HappyFox API first?

No. Cotlet works in your own HappyFox account and uses no API key or auth code. HappyFox's own API needs an admin to enable the API app under Apps > Goodies > API, and an account that signed up recently may have that setting switched off until you ask support@happyfox.com.

What can it not do yet?

Tickets are worked as text: nothing uploads attachments, and a sent reply cannot be recalled. Not built yet: creating tickets, merging tickets, bulk actions, contacts, assets and knowledge base articles. Your role still counts: a call without the permission fails with APP_PERMISSION_DENIED.

Should I use a HappyFox MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when HappyFox changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with HappyFox?

No. Cotlet is independent and not affiliated with HappyFox.

Give your agent access to HappyFox.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free