FreeScout API and MCP server

FreeScout needs a paid module for its API, and that API cannot merge conversations. Sign in to FreeScout 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.

Not affiliated with FreeScout.

FreeScout's own API leaves this out. So we run one for you.

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

Checked Oct 23, 2026. Sources: FreeScout: API & Webhooks module · FreeScout API docs · FreeScout Wiki: FAQ · FreeScout: Workflows module

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

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

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect FreeScout 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. FreeScout 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/freescout with its own method and path, such as PUT /api/v1/freescout/conversations/{conversation_id}/status, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the FreeScout API and MCP server do?

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

FreeScout tools in Cotlet's MCP server and REST API
Tool What it does Access
list_mailboxes Mailboxes your FreeScout account can open, with their IDs and email addresses. read
list_users The people you can assign conversations to in one mailbox. read
list_conversations Conversations of one mailbox by status, assignee or search text, with who wrote last. read
get_conversation One conversation with every thread, oldest first, internal notes marked. read
list_customers Customers matching a name, email address or phone number. read
get_customer A customer profile with the conversations they started. read
add_note Add an internal note to a conversation. The customer does not see it. writeasks first
reply_to_customer Send a reply to the customer, or save it as a draft for you to send. writeasks first
set_conversation_status Set a conversation to Active, Pending, Closed or Spam. write
assign_conversation Assign a conversation to a teammate, or leave user_id out to unassign it. writeasks first
move_conversation Move a conversation to another mailbox. writeasks first
merge_conversations Merge one conversation into another. writeasks first

Scroll the table for all 12 tools.

Ask in plain words. Your agent does the rest.

Is it safe to connect FreeScout?

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+.

How much do the FreeScout 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. Each call uses 10 credits, and your Cloud Browser uses 50 credits a day while FreeScout is enabled for agents, so 20 calls a day come to 250 credits.

Cotlet credit packs: price, credits and calls at 10 credits each
Credits Price, one time Calls at 10 credits Per 1,000 credits
5,000 $29 500 $5.80
15,000 $79 1,500 $5.27
32,000 $149 3,200 $4.66
60,000 $249 6,000 $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 FreeScout have an API?

FreeScout has a REST API, but only through its paid API & Webhooks module, and it has no official MCP server (checked 23 Oct 2026). The module is a lifetime license for one FreeScout instance. The API reads and writes conversations, threads, customers and users, and it has no endpoint to merge conversations.

How do I get access?

Sign up free, open FreeScout 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 FreeScout yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so FreeScout 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: add_note, reply_to_customer, assign_conversation, move_conversation, merge_conversations wait for your OK by default. You can switch that off per tool for scheduled runs.

Can Cotlet reach a FreeScout on a private network?

Only if your FreeScout address opens from the internet. Cotlet signs in from a Cloud Browser in the EU, so an instance that answers only inside a company network or behind a VPN is out of reach. FreeScout is self-hosted, on your own server or on a managed host.

Which FreeScout role does my agent need?

Your agent can do what the signed-in account can do. A non-admin FreeScout profile can have "User can see only assigned conversations", which hides unassigned ones, and other agents see only the mailboxes they were given. Use an account that sees the mailboxes you want worked.

Should I use a FreeScout 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 FreeScout 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 FreeScout?

No. Cotlet is independent and not affiliated with FreeScout.

Give your agent access to FreeScout.

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