[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # HappyFox API and MCP server > 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. Help desk software: tickets from email, chat and forms in queues, with statuses, priorities, categories, canned actions and smart rules that route and answer them. ## What is the HappyFox API? Cotlet's HappyFox API exposes 12 endpoints for your own HappyFox account: search tickets, get ticket, list queues, list categories, list statuses, list priorities, list agents, list canned actions, reply to ticket, add private note, update ticket and apply canned action. The search_tickets endpoint returns tickets in a queue or matching a text search, with status, priority, category and assignee. Each endpoint takes simple JSON inputs like ticket_id, query or body and works both as an operation of the happyfox_read or happyfox_write MCP tool for agents and as a REST call for scripts. - **Category:** [Customer support](https://cotlet.dev/integrations/category/customer-support.md) - **Endpoints:** 12 (8 read, 4 write) - **Updated:** 2026-10-20 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). Cotlet is a hosted MCP server and REST API for HappyFox with 12 endpoints (8 read, 4 write): you sign in once in your own cloud browser, your AI agent does the work. ## Does HappyFox have an official 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. | Task | HappyFox official | Cotlet | |---|---|---| | Search and list tickets | Yes: Tickets API, paged; you write the paging and filters | Yes | | Read a ticket with its updates | Yes: Tickets API | Yes | | Reply to the contact | Yes: Staff update call; no MCP server for agents | Yes | | Add a private note | Yes: Staff private note call, with an option to alert subscribers or agents | Yes | | Set status, priority, assignee and tags | Yes: Staff update call, with IDs you look up first | Yes | | Apply a canned action | Partly: The API sets the same fields and takes your reply text; the saved canned action is chosen in the ticket editor | Yes | | List queues | Partly: The API lists tickets by status; queues are set up in the app | Yes | | List categories, statuses, priorities and agents | Yes: Lookup calls that return the IDs | Yes | Sources: [HappyFox Support: API Reference, Tickets API Endpoints](https://support.happyfox.com/kb/article/1039-happyfox-api-documentation/), [HappyFox Support: How to create an API Key and Auth Code](https://support.happyfox.com/kb/article/476-create-api-key-auth-code-happyfox/), [HappyFox Support: Enabling API in your HappyFox account](https://support.happyfox.com/kb/article/221-enabling-api-in-your-happyfox-account/), [Zapier: HappyFox integrations](https://zapier.com/apps/happyfox/integrations) ## For AI agents ```text 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. Cotlet provides a hosted MCP server and REST API for HappyFox: 12 tools (8 read, 4 write). Access Sign up at https://cotlet.dev/app/signup?app=happyfox, then request the app and create API keys in the Cotlet console. MCP server https://cotlet.dev/mcp/v1 MCP tools happyfox_read, happyfox_write, reads and writes apart; call one with {"operation": "", "arguments": {...}} REST base https://cotlet.dev/api/v1/happyfox, each operation at its own route, e.g. PATCH /api/v1/happyfox/tickets/{ticket_id} Auth Authorization: Bearer . Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in. Operations search_tickets, get_ticket, list_queues, list_categories, list_statuses, list_priorities, list_agents, list_canned_actions, reply_to_ticket, add_private_note, update_ticket, apply_canned_action Confirm reply_to_ticket, add_private_note, update_ticket, apply_canned_action (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations) Markdown https://cotlet.dev/integrations/happyfox-api-mcp-server.md How access works: 1. The user signs up at https://cotlet.dev/app/signup?app=happyfox, requests HappyFox in the Cotlet console and creates an API key there. 2. The user signs in to HappyFox once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables HappyFox for agents. An agent cannot do this step. 3. The API key goes into the MCP client or the REST call as a bearer token. Fits: people who want a hosted HappyFox server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source HappyFox MCP server instead. Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA. Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev. Sign-in: the user signs in to HappyFox in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get HappyFox only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273). API key: holds no HappyFox login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once. Terms: the user stays responsible for following HappyFox's terms; Cotlet is not affiliated with HappyFox. ``` ## What can an AI agent do in HappyFox? Cotlet is best for HappyFox support teams who want an AI agent to triage tickets, send replies and notes and chase pending ones without running or fixing a server. - **[Triage new support tickets](https://cotlet.dev/integrations/happyfox-api-mcp-server/triage-new-support-tickets.md)** (runs: daily): "Go through the Unresponded Tickets queue in HappyFox. Set priority from what the customer wrote, assign billing questions to the Billing agent, add a tag and leave a one-line private note with the reason. Leave unclear ones for me." → `list_queues`, `search_tickets`, `get_ticket`, `list_priorities`, `list_agents`, `update_ticket`, `add_private_note` - **[Reply to common questions with canned actions](https://cotlet.dev/integrations/happyfox-api-mcp-server/reply-with-canned-actions.md)** (runs: daily): "Look at open HappyFox tickets with no reply. Where a canned action clearly fits, such as the password reset steps, apply it as a reply. Show me the ticket and the canned action for anything uncertain." → `list_canned_actions`, `search_tickets`, `get_ticket`, `apply_canned_action` - **[Follow up on pending tickets](https://cotlet.dev/integrations/happyfox-api-mcp-server/follow-up-on-pending-tickets.md)** (runs: daily): "Find HappyFox tickets in the Pending Tickets queue with no reply from the customer for 3 days. Send a short reminder that quotes what we asked for. If we already sent a reminder, tell me instead of sending a second one." → `list_queues`, `search_tickets`, `get_ticket`, `reply_to_ticket` - **Summarize long tickets for handoff**: "For every ticket assigned to me with more than 10 updates, add a private note with a 3-line summary: the problem, what we tried, what is open." → `search_tickets`, `get_ticket`, `add_private_note` - **Weekly support backlog report** (runs: weekly): "Every Monday, tell me how many HappyFox tickets are pending per category, the oldest ticket in each queue, and anything high priority with no assignee." → `list_queues`, `list_categories`, `search_tickets` ## Can HappyFox automations run on a schedule in n8n, Make or Zapier? Yes. Cotlet does not replace your automation platform: it gives it a HappyFox connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to triage new support tickets, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off. | Where | How to connect | How to schedule | |---|---|---| | Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. | | n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/happyfox/queues. | Schedule Trigger node. | | Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. | | Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. | | Your own script | GET https://cotlet.dev/api/v1/happyfox/queues with your API key. | cron or GitHub Actions. | ## Tools **For AI agents:** Every endpoint and its schema is public. The 12 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to HappyFox. ### search_tickets Tickets in a queue or matching a text search, with status, priority, category and assignee. Access: read. REST: `GET /api/v1/happyfox/tickets/search`. MCP: `happyfox_read → search_tickets`. | Parameter | Type | Required | Description | |---|---|---|---| | `queue_id` | integer | no | Queue ID from list_queues. Default: All Tickets. | | `query` | string | no | Words to find in the subject or text. | | `limit` | integer | no | 1 to 50. Default: 25. | | `cursor` | string | no | Next page cursor from the previous call. | Returns tickets without their updates, newest first. Pass queue_id from list_queues to read one queue, query for words in the subject or text, or both. Pages hold up to 50 tickets; pass next_cursor back as cursor for the next page. Use get_ticket for the full thread. Example response: ```json { "tickets": [ { "ticket_id": 2038, "subject": "Refund for double charge", "status": "New", "priority": null, "category": "Billing", "contact": "Maya Brandt", "assignee": null, "tags": [], "updated_at": "2026-10-19T06:41:00Z" } ], "next_cursor": null } ``` ### get_ticket One ticket with its fields, tags and every update, staff replies, contact messages and private notes. Access: read. REST: `GET /api/v1/happyfox/tickets/{ticket_id}`. MCP: `happyfox_read → get_ticket`. | Parameter | Type | Required | Description | |---|---|---|---| | `ticket_id` | integer | yes | Ticket ID from search_tickets. | Returns subject, status, priority, category, contact, assignee, tags and all updates in order, oldest first. Each update says whether it is a contact message, a staff reply or a private note, and who wrote it. Use it before replying so your agent sees the whole thread. Example response: ```json { "ticket_id": 2011, "subject": "Export fails with an error", "status": "Awaiting customer", "priority": "Medium", "category": "Support", "contact": { "name": "Dana Whitfield", "email": "dana@example.com" }, "assignee": "Sam Okafor", "tags": [ "export", "web" ], "updates": [ { "kind": "contact_message", "author": "Dana Whitfield", "body": "Export to CSV fails every time.", "created_at": "2026-10-15T08:55:00Z" }, { "kind": "staff_reply", "author": "Sam Okafor", "body": "Sorry about that. What error text do you see after clicking Export?", "created_at": "2026-10-15T09:30:00Z" } ] } ``` ### list_queues Ticket queues you can open: the ready-made ones and the ones your team set up. Access: read. REST: `GET /api/v1/happyfox/queues`. MCP: `happyfox_read → list_queues`. No parameters. Lists the queues your agent user can see with their IDs and names. HappyFox ships Pending Tickets, All Tickets, Unresponded Tickets and Assigned to Me. Pass queue_id to search_tickets. Example response: ```json { "queues": [ { "queue_id": 1, "name": "Pending Tickets" }, { "queue_id": 2, "name": "All Tickets" }, { "queue_id": 3, "name": "Unresponded Tickets" }, { "queue_id": 4, "name": "Assigned to Me" } ] } ``` ### list_categories Ticket categories with ID and name. Access: read. REST: `GET /api/v1/happyfox/categories`. MCP: `happyfox_read → list_categories`. No parameters. Lists the categories in your HappyFox with their IDs and names. Canned actions are defined per category, so use it before picking one. Example response: ```json { "categories": [ { "category_id": 1, "name": "Support" }, { "category_id": 2, "name": "Billing" } ] } ``` ### list_statuses Ticket statuses with ID, name and behaviour, pending or completed. Access: read. REST: `GET /api/v1/happyfox/statuses`. MCP: `happyfox_read → list_statuses`. No parameters. Lists the statuses your admin set up under Manage >> Statuses. Behaviour says whether a status leaves the ticket unresolved (pending) or resolved (completed). Use status_id with update_ticket. Example response: ```json { "statuses": [ { "status_id": 1, "name": "New", "behavior": "pending", "default": true }, { "status_id": 2, "name": "Awaiting customer", "behavior": "pending", "default": false }, { "status_id": 3, "name": "Closed", "behavior": "completed", "default": false } ] } ``` ### list_priorities Ticket priorities with ID and name. Access: read. REST: `GET /api/v1/happyfox/priorities`. MCP: `happyfox_read → list_priorities`. No parameters. Lists the priorities your HappyFox uses with their IDs and names, as your admin named them. Use priority_id with update_ticket. Example response: ```json { "priorities": [ { "priority_id": 2, "name": "Low" }, { "priority_id": 3, "name": "Medium" }, { "priority_id": 4, "name": "High" } ] } ``` ### list_agents Agents who can be assigned tickets, with ID, name and role. Access: read. REST: `GET /api/v1/happyfox/agents`. MCP: `happyfox_read → list_agents`. | Parameter | Type | Required | Description | |---|---|---|---| | `query` | string | no | Only agents whose name or email contains this text. | Lists the staff in your HappyFox with ID, name and role. Use assignee_id with update_ticket. What your agent user can see depends on its role. Example response: ```json { "agents": [ { "agent_id": 12, "name": "Sam Okafor", "role": "Agent" }, { "agent_id": 3, "name": "Lena Ortiz", "role": "Admin" } ] } ``` ### list_canned_actions Canned actions with ID, name and the categories they are defined for. Access: read. REST: `GET /api/v1/happyfox/canned-actions`. MCP: `happyfox_read → list_canned_actions`. | Parameter | Type | Required | Description | |---|---|---|---| | `category_id` | integer | no | Only canned actions defined for this category. | Lists the canned actions your agent user can use, from Automate >> Canned Actions. A canned action shows in the ticket editor only for categories it is defined for, so the list carries them. Pass canned_action_id to apply_canned_action. Example response: ```json { "canned_actions": [ { "canned_action_id": 31, "name": "Password reset steps", "categories": [ "Support" ] }, { "canned_action_id": 44, "name": "Invoice copy", "categories": [ "Billing" ] } ] } ``` ### reply_to_ticket Send a reply to the contact and optionally set the status in the same call. Access: write, asks the user first. REST: `POST /api/v1/happyfox/tickets/{ticket_id}/replies`. MCP: `happyfox_write → reply_to_ticket`. | Parameter | Type | Required | Description | |---|---|---|---| | `ticket_id` | integer | yes | Ticket ID from search_tickets. | | `body` | string | yes | Reply text, sent to the contact. | | `status_id` | integer | no | Status ID from list_statuses. Default: leave the status as it is. | Adds a staff reply to the ticket, which emails the contact. A sent reply stays in the ticket history. Set status_id in the same call to move the ticket on with the reply. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "ticket_id": 2011, "update_id": 88120, "kind": "staff_reply", "status": "Awaiting customer", "created_at": "2026-10-20T09:00:00Z" } ``` ### add_private_note Add a note only your team can see, and optionally alert subscribers or agents. Access: write, asks the user first. REST: `POST /api/v1/happyfox/tickets/{ticket_id}/private-notes`. MCP: `happyfox_write → add_private_note`. | Parameter | Type | Required | Description | |---|---|---|---| | `ticket_id` | integer | yes | Ticket ID from search_tickets. | | `body` | string | yes | Note text, visible to staff only. | | `notify` | enum | no | none, subscribers or category_agents. Default: none. | Adds a private note that the contact never sees. notify can alert the ticket's subscribers or the agents in its category, and an alert is a message to colleagues. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "ticket_id": 2038, "update_id": 88131, "kind": "private_note", "notified": "none", "created_at": "2026-10-20T09:01:00Z" } ``` ### update_ticket Change status, priority, assignee or tags of one ticket. Access: write, asks the user first. REST: `PATCH /api/v1/happyfox/tickets/{ticket_id}`. MCP: `happyfox_write → update_ticket`. | Parameter | Type | Required | Description | |---|---|---|---| | `ticket_id` | integer | yes | Ticket ID from search_tickets. | | `status_id` | integer | no | Status ID from list_statuses. | | `priority_id` | integer | no | Priority ID from list_priorities. | | `assignee_id` | integer | no | Agent ID from list_agents, or null to leave the ticket unassigned. | | `add_tags` | array | no | Tags to add. Existing tags stay. | Updates the fields you pass and leaves the rest. Use IDs from list_statuses, list_priorities and list_agents. Pass assignee_id null to leave the ticket unassigned. Smart Rules and SLA run as usual after the update, so a status change can email the contact. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "ticket_id": 2038, "status": "New", "priority": "High", "assignee": "Sam Okafor", "tags": [ "billing", "refund" ], "updated_at": "2026-10-20T09:02:00Z" } ``` ### apply_canned_action Apply a canned action to a ticket as a reply or a private note and submit it. Access: write, asks the user first. REST: `POST /api/v1/happyfox/tickets/{ticket_id}/canned-actions/{canned_action_id}/apply`. MCP: `happyfox_write → apply_canned_action`. | Parameter | Type | Required | Description | |---|---|---|---| | `ticket_id` | integer | yes | Ticket ID from search_tickets. | | `canned_action_id` | integer | yes | Canned action ID from list_canned_actions. | | `mode` | enum | no | reply or private_note. Default: reply. | Picks the canned action in the ticket editor, fills in its response and property changes, and submits. mode reply emails the contact; mode private_note does not. The action must be defined for the ticket's category, or the call fails and lists the actions that are. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "ticket_id": 2090, "update_id": 88140, "mode": "reply", "canned_action": "Password reset steps", "changed": { "status": "Awaiting customer" }, "created_at": "2026-10-20T09:03:00Z" } ``` ## How do I connect HappyFox to Claude Code, Codex or Cursor? Connecting HappyFox takes three steps: sign up, sign in to HappyFox once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key. ### Connect HappyFox to your agent. 1. **Create an account** Sign up and add HappyFox in the console. Your API key is there too. 2. **Sign in to HappyFox in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to HappyFox there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off. 3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once. 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" ``` 4. **Ask your agent** Ask in plain words. Your agent finds the HappyFox tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool. ``` Go through the Unresponded Tickets queue in HappyFox. Set priority from what the customer wrote, assign billing questions to the Billing agent, add a tag and leave a one-line private note with the reason. Leave unclear ones for me. ``` ### Call HappyFox from your scripts. 1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code. ``` export COTLET_API_KEY="cotlet_..." ``` 2. **Call a tool** Every tool is an endpoint under /api/v1/happyfox with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise. ``` curl -X PATCH https://cotlet.dev/api/v1/happyfox/tickets/2038 \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"priority_id":4,"assignee_id":12,"add_tags":["billing","refund"]}' ``` 3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing. ``` { "ticket_id": 2038, "status": "New", "priority": "High", "assignee": "Sam Okafor", "tags": [ "billing", "refund" ], "updated_at": "2026-10-20T09:02:00Z" } ``` ## Why use Cotlet for HappyFox? **Built for agents** - One MCP server for every app you connect. - The same tools as a REST API for scripts and cron jobs. - Works with Claude Code, Codex and Cursor. **Your login stays yours** - You sign in to HappyFox yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses. - A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory. - The model never sees a login. - No stored passwords, no CAPTCHA solving, no MFA bypass. **You stay in control** - Scope each API key: its apps, its tools, read only or read and write. - Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you. - Every background request listed in your Background activity. Disable for agents in one click. **Kept working for you** - We test every integration every 6 hours. - When HappyFox changes, the tool pauses until we fix it. - Failed calls cost nothing. ## Is it safe to connect HappyFox to Cotlet? Yes. You sign in to HappyFox yourself, in your own Cloud Browser, and we never save your password. Your agents only get HappyFox once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself. - **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev) - **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on) - **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev) - **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev) [How Cotlet protects your access](https://cotlet.dev/security.md) ### Common concerns **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 this an official HappyFox integration?** No, Cotlet is independent of HappyFox. HappyFox's own API is too limited for this work. Cotlet works through your own HappyFox account, the way you use HappyFox in the browser, so you need no partner approval and no developer setup. **What about client data and GDPR?** Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it. **Can I start with read only?** Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool. **Is it reliable?** Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev. **How do I stop?** Press Disable for agents next to HappyFox in your console: your agents lose access at once and you stay signed in. Signing out of HappyFox in the browser works too, and Reset browser deletes the whole profile. ## Is there a HappyFox MCP server on GitHub? Yes. Community HappyFox MCP servers exist on GitHub, usually maintained by one person. You install one yourself, give it an API key and auth code, and fix it when HappyFox changes. Cotlet hosts the same kind of server for you, signs in as your agent user, and our team keeps it working. | | GitHub MCP server | Cotlet | |---|---|---| | Setup | Clone the repo, enable the API app, create a key and auth code, add the server to each MCP client | Sign up, sign in to HappyFox once, add one MCP server or API key | | When HappyFox changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free | | Your HappyFox access | API key and auth code in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click | | When access expires | Tools fail until you replace the key or sign in again by hand | Your Cloud Browser keeps you signed in; if HappyFox logs you out, your agent gets a link to sign in again | | Upkeep | You update, monitor and debug it yourself | Nothing to host or update | | Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule | | Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription | ### Which one fits you **Pick Cotlet if** - you are not a developer, or you do not want to maintain a server - you need it to keep working when HappyFox changes, without checking it yourself - your agent or a script should run it on a schedule, also while your computer is off **Pick an open-source server if** - you are comfortable installing, updating and fixing it yourself - you want your sign-in to stay on your own computer - you only need it now and then, from one MCP client ## How much does the HappyFox API cost? Free 7-day trial with 2,000 credits, no card needed. After that, the HappyFox API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over. | 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. [See full pricing](https://cotlet.dev/pricing.md) ## How Cotlet holds your access Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own HappyFox account. - **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms) - **Your sign-in:** You sign in to HappyFox yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get HappyFox only after you enable it. When HappyFox signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md) - **Revoking access:** Press Disable for agents next to HappyFox, sign out of HappyFox in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool. - **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA. - **HappyFox's terms:** You use your own HappyFox account and stay responsible for following HappyFox's terms. Cotlet is independent and not affiliated with HappyFox. [Terms](https://cotlet.dev/terms) - **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev) ## Frequently asked questions **How do I get access?** Sign up free, open HappyFox in the console and press Request access. Then you create your API key and connect HappyFox there. **Do I need to be technical?** No. You sign in to HappyFox once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix. **Is it safe to connect HappyFox to Cotlet?** Yes. You sign in to HappyFox yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get HappyFox once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security. **Is a hosted server safer than a local one? My HappyFox sign-in would leave my computer.** On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your HappyFox cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off. **Why does Cotlet send requests instead of clicking in my browser?** To be fast, Cotlet doesn't click through HappyFox's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. HappyFox sees the same browser and IP you signed in with, and every request is listed in your Background activity. **What if someone gets my Cotlet API key?** The key holds no HappyFox login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once. **Why a signed-in browser and not OAuth, like other integration platforms?** HappyFox offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273). **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. **Can my agent post or send messages in HappyFox without asking me?** No. Every call to reply_to_ticket, add_private_note, update_ticket or apply_canned_action waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. **Can I use the HappyFox API in n8n?** Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/happyfox from the HTTP Request node. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners. ## For AI agents: sign your user up Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed. 1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests 2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them. 3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests. One call creates the account and sends the access request; we email the user when access is granted.