[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)

# FreeScout API and MCP server

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

Free open source help desk and shared inbox that you host yourself: email and chat conversations, internal notes, assignment and paid modules for workflows, a knowledge base and reports.

## What is the FreeScout API?

Cotlet's FreeScout API exposes 12 endpoints for your own FreeScout account: list mailboxes, list assignable users, list conversations, get conversation, list customers, get customer, add internal note, reply to customer, set conversation status, assign conversation, move conversation and merge conversations. The list_mailboxes endpoint returns mailboxes your FreeScout account can open, with their IDs and email addresses. Each endpoint takes simple JSON inputs like conversation_id, mailbox_id or status and works both as an operation of the freescout_read or freescout_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 (6 read, 6 write)
- **Updated:** 2026-10-18

FreeScout has a REST API, but only through its paid API & Webhooks module, and it has no official MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for FreeScout with 12 endpoints (6 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does FreeScout have an official 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.

| Task | FreeScout official | Cotlet |
|---|---|---|
| List and read conversations | Partly: Needs the paid API & Webhooks module | Yes |
| Reply to a customer or save a draft | Partly: Needs the paid API & Webhooks module | Yes |
| Add an internal note | Partly: Needs the paid API & Webhooks module | Yes |
| Change status, including Spam | Partly: Needs the paid API & Webhooks module | Yes |
| Assign a conversation | Partly: Needs the paid API & Webhooks module | Yes |
| Move a conversation to another mailbox | Partly: Needs the paid API & Webhooks module | Yes |
| Merge conversations | No: The API docs list no merge endpoint | Yes |
| Read customers and their conversations | Partly: Needs the paid API & Webhooks module | Yes |

Sources: [FreeScout: API & Webhooks module](https://freescout.net/module/api-webhooks/), [FreeScout API docs](https://api-docs.freescout.net/), [FreeScout Wiki: FAQ](https://github.com/freescout-help-desk/freescout/wiki/FAQ), [FreeScout: Workflows module](https://freescout.net/module/workflows/)

## Quick reference

```text
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.
Cotlet provides a hosted MCP server and REST API for FreeScout: 12 tools (6 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=freescout, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    freescout_read, freescout_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/freescout, each operation at its own route, e.g. PUT /api/v1/freescout/conversations/{conversation_id}/status
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_mailboxes, list_users, list_conversations, get_conversation, list_customers, get_customer, add_note, reply_to_customer, set_conversation_status, assign_conversation, move_conversation, merge_conversations
Confirm      add_note, reply_to_customer, assign_conversation, move_conversation, merge_conversations (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/freescout-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=freescout, requests FreeScout in the Cotlet console and creates an API key there.
2. The user signs in to FreeScout once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables FreeScout 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 FreeScout 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 FreeScout 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 FreeScout 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 FreeScout 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 FreeScout 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 FreeScout's terms; Cotlet is not affiliated with FreeScout.
```

## What can an AI agent do in FreeScout?

Cotlet is best for FreeScout support teams who want their AI agent to draft replies, merge duplicates and sort the queue without running or fixing a server.

- **[Draft replies to waiting customers](https://cotlet.dev/integrations/freescout-api-mcp-server/draft-replies-to-waiting-customers.md)** (runs: daily): "Go through the active conversations in my Support mailbox where the customer wrote last. Read the thread and any notes, and save a draft reply for each one you can answer. Leave refunds and legal questions for me." → `list_conversations`, `get_conversation`, `reply_to_customer`
- **[Merge duplicate conversations](https://cotlet.dev/integrations/freescout-api-mcp-server/merge-duplicate-conversations.md)** (runs: weekly): "Find active conversations in my Support mailbox where the same customer wrote twice about the same problem. Merge the newer one into the older one and list pairs you are unsure about." → `list_conversations`, `get_conversation`, `merge_conversations`
- **[Assign unassigned conversations](https://cotlet.dev/integrations/freescout-api-mcp-server/assign-unassigned-conversations.md)** (runs: daily): "Read the unassigned conversations in my Support mailbox. Assign billing questions to Sam Okafor and technical ones to Maya Brown, and add a note saying why. Leave the rest." → `list_users`, `list_conversations`, `get_conversation`, `assign_conversation`, `add_note`
- **Close stale pending conversations** (runs: weekly): "List pending conversations in my Support mailbox where the customer has not answered for 14 days. Close them and tell me which ones I should look at first." → `list_conversations`, `get_conversation`, `set_conversation_status`
- **Daily queue summary** (runs: daily): "For each of my mailboxes, tell me how many active conversations are unassigned and which one has waited longest." → `list_mailboxes`, `list_conversations`
- **Check a customer before you answer**: "Look up lena@example.com in FreeScout and summarise her earlier conversations before I reply." → `list_customers`, `get_customer`, `get_conversation`

## Can FreeScout automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a FreeScout 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 draft replies to waiting customers, 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/freescout/mailbox/{mailbox_id}/conversations. | 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/freescout/mailbox/{mailbox_id}/conversations 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 FreeScout.

### list_mailboxes

Mailboxes your FreeScout account can open, with their IDs and email addresses. Access: read. REST: `GET /api/v1/freescout/mailboxes`. MCP: `freescout_read → list_mailboxes`.

No parameters.

Returns the mailboxes your login has access to. mailbox_id is the number at the end of the mailbox settings address, and the other tools take it. An admin sees all mailboxes; other agents see the ones they were given.

Example response:

```json
{
  "mailboxes": [
    {
      "mailbox_id": 1,
      "name": "Support",
      "email": "support@yourcompany.com"
    },
    {
      "mailbox_id": 2,
      "name": "Sales",
      "email": "sales@yourcompany.com"
    }
  ]
}
```

### list_users

The people you can assign conversations to in one mailbox. Access: read. REST: `GET /api/v1/freescout/mailbox/{mailbox_id}/users`. MCP: `freescout_read → list_users`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `mailbox_id` | integer | yes | Mailbox ID from list_mailboxes. It is the number at the end of the mailbox settings address. |

Returns the names in the Assignee dropdown of the mailbox, with their user_id. A mailbox can hide admins from that list with its "Hide from Assign list" permission, so a hidden admin is not returned. Use user_id with assign_conversation.

Example response:

```json
{
  "users": [
    {
      "user_id": 2,
      "name": "Maya Brown"
    },
    {
      "user_id": 3,
      "name": "Sam Okafor"
    }
  ]
}
```

### list_conversations

Conversations of one mailbox by status, assignee or search text, with who wrote last. Access: read. REST: `GET /api/v1/freescout/mailbox/{mailbox_id}/conversations`. MCP: `freescout_read → list_conversations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `mailbox_id` | integer | yes | Mailbox ID from list_mailboxes. It is the number at the end of the mailbox settings address. |
| `status` | string | no | active, pending, closed or spam. Default active. |
| `assigned_to` | string | no | A user_id from list_users, or unassigned. |
| `query` | string | no | Search text. Use #12345 to find a conversation by its number. |
| `page` | integer | no | Page number, starting at 1. Follow it while has_more is true. |

Returns conversations of one mailbox in the order FreeScout lists them, one page at a time; follow page while has_more is true. status defaults to active. last_reply_from says whether the customer or a teammate wrote last, and waiting_since is the time of the customer message nobody has answered. Deleted conversations are left out. Putting # in front of a number in query finds that conversation number.

Example response:

```json
{
  "conversations": [
    {
      "conversation_id": 4821,
      "number": 1207,
      "subject": "Invoice shows the wrong VAT number",
      "customer": {
        "name": "Lena Ortiz",
        "email": "lena@example.com"
      },
      "status": "active",
      "assignee": null,
      "last_reply_from": "customer",
      "waiting_since": "2026-10-21T14:05:00Z",
      "preview": "Our invoice from October lists the wrong VAT number. Can you fix it?"
    },
    {
      "conversation_id": 4833,
      "number": 1219,
      "subject": "Re: Invoice shows the wrong VAT number",
      "customer": {
        "name": "Lena Ortiz",
        "email": "lena@example.com"
      },
      "status": "active",
      "assignee": null,
      "last_reply_from": "customer",
      "waiting_since": "2026-10-22T09:40:00Z",
      "preview": "Still no answer on my invoice. Who can help?"
    }
  ],
  "page": 1,
  "has_more": false
}
```

### get_conversation

One conversation with every thread, oldest first, internal notes marked. Access: read. REST: `GET /api/v1/freescout/conversations/{conversation_id}`. MCP: `freescout_read → get_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | Conversation ID from list_conversations or get_conversation. It is not the #number shown in the list. |

Returns the subject, status, assignee, customer and all threads oldest first. type is customer for a customer message, message for a reply from your team and note for an internal note. Attachments are listed by file name; their contents are not downloaded. Use it before replying so a draft matches what the notes say.

Example response:

```json
{
  "conversation_id": 4821,
  "number": 1207,
  "subject": "Invoice shows the wrong VAT number",
  "mailbox_id": 1,
  "status": "active",
  "assignee": null,
  "customer": {
    "customer_id": 311,
    "name": "Lena Ortiz",
    "email": "lena@example.com"
  },
  "threads": [
    {
      "type": "customer",
      "from": "Lena Ortiz",
      "created_at": "2026-10-21T14:05:00Z",
      "body": "Our invoice from October lists the wrong VAT number. Can you fix it?"
    },
    {
      "type": "note",
      "from": "Sam Okafor",
      "created_at": "2026-10-22T08:30:00Z",
      "body": "Billing checked: the VAT ID on file is right, the invoice template is old."
    }
  ]
}
```

### list_customers

Customers matching a name, email address or phone number. Access: read. REST: `GET /api/v1/freescout/customers`. MCP: `freescout_read → list_customers`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Name, email address or phone number. |
| `page` | integer | no | Page number, starting at 1. Follow it while has_more is true. |

Searches the customers of your FreeScout, one page at a time. A customer can have several email addresses, and all of them are returned. FreeScout keeps one customer table for all mailboxes, so a customer may appear with conversations from several of them.

Example response:

```json
{
  "customers": [
    {
      "customer_id": 311,
      "name": "Lena Ortiz",
      "emails": [
        "lena@example.com"
      ],
      "phone": "+1 555 0142"
    }
  ],
  "page": 1,
  "has_more": false
}
```

### get_customer

A customer profile with the conversations they started. Access: read. REST: `GET /api/v1/freescout/customers/{customer_id}`. MCP: `freescout_read → get_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `customer_id` | integer | yes | Customer ID from list_customers or get_conversation. |

Returns the profile, all email addresses and the customer's conversations with subject and status. Use it to see earlier problems before you answer, or to find a second conversation from the same person.

Example response:

```json
{
  "customer_id": 311,
  "name": "Lena Ortiz",
  "emails": [
    "lena@example.com"
  ],
  "phone": "+1 555 0142",
  "conversations": [
    {
      "conversation_id": 4821,
      "number": 1207,
      "subject": "Invoice shows the wrong VAT number",
      "status": "active"
    },
    {
      "conversation_id": 4410,
      "number": 1096,
      "subject": "How do I add a second user?",
      "status": "closed"
    }
  ]
}
```

### add_note

Add an internal note to a conversation. The customer does not see it. Access: write, asks the user first. REST: `POST /api/v1/freescout/conversations/{conversation_id}/notes`. MCP: `freescout_write → add_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | Conversation ID from list_conversations or get_conversation. It is not the #number shown in the list. |
| `body` | string | yes | Text of the note. |

Adds a note under your name, the same as Add Note in the conversation. Notes are for your team and are not sent to the customer. A note cannot be removed with one call from Cotlet, so keep it short. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "conversation_id": 4850,
  "thread_type": "note",
  "created_at": "2026-10-23T08:12:00Z"
}
```

### reply_to_customer

Send a reply to the customer, or save it as a draft for you to send. Access: write, asks the user first. REST: `POST /api/v1/freescout/conversations/{conversation_id}/customer/replies`. MCP: `freescout_write → reply_to_customer`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | Conversation ID from list_conversations or get_conversation. It is not the #number shown in the list. |
| `body` | string | yes | Text of the reply. |
| `draft` | boolean | no | true saves a draft and sends nothing. Default false. |
| `status_after` | string | no | active, pending or closed. Leave out to keep what the Send dropdown shows by default. |

Writes a reply under your name. With draft set to true the text is saved in FreeScout as a draft, nothing leaves FreeScout, and you finish it with Edit Draft. Without draft the email goes to the customer at once. status_after sets the status once the reply is sent, like the Send dropdown. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "conversation_id": 4821,
  "thread_type": "message",
  "state": "draft",
  "url": "https://support.yourcompany.com/conversation/4821"
}
```

### set_conversation_status

Set a conversation to Active, Pending, Closed or Spam. Access: write. REST: `PUT /api/v1/freescout/conversations/{conversation_id}/status`. MCP: `freescout_write → set_conversation_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | Conversation ID from list_conversations or get_conversation. It is not the #number shown in the list. |
| `status` | string | yes | active, pending, closed or spam. |

Changes the status of one conversation, the same as the Status dropdown. It sends nothing to the customer and one more call sets it back, so it does not wait for your OK. FreeScout has only these four statuses. If your team has a Workflows rule that emails the customer on closing, that rule still runs.

Example response:

```json
{
  "conversation_id": 4790,
  "status": "closed",
  "changed_at": "2026-10-23T08:20:00Z"
}
```

### assign_conversation

Assign a conversation to a teammate, or leave user_id out to unassign it. Access: write, asks the user first. REST: `POST /api/v1/freescout/conversations/{conversation_id}/assign`. MCP: `freescout_write → assign_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | Conversation ID from list_conversations or get_conversation. It is not the #number shown in the list. |
| `user_id` | integer | no | User ID from list_users. Leave out to unassign. |

Sets the assignee of one conversation. user_id must be a person returned by list_users for that mailbox. The teammate gets an email about it if their Notifications are set up for that. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "conversation_id": 4850,
  "assignee": {
    "user_id": 3,
    "name": "Sam Okafor"
  },
  "status": "active"
}
```

### move_conversation

Move a conversation to another mailbox. Access: write, asks the user first. REST: `POST /api/v1/freescout/mailbox/{mailbox_id}/conversations/{conversation_id}/move`. MCP: `freescout_write → move_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | Conversation ID from list_conversations or get_conversation. It is not the #number shown in the list. |
| `mailbox_id` | integer | yes | ID of the target mailbox from list_mailboxes. |

Moves the conversation with the Move action. In FreeScout the original message can no longer be shown after a move, and a Workflows rule does not run on a moved conversation unless it has the condition for conversations moved from another mailbox. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "conversation_id": 4862,
  "mailbox_id": 2,
  "moved_from": 1
}
```

### merge_conversations

Merge one conversation into another. Access: write, asks the user first. REST: `POST /api/v1/freescout/merge-intos/{merge_into_id}/conversations/{conversation_id}/merge`. MCP: `freescout_write → merge_conversations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | The conversation to merge, from list_conversations. |
| `merge_into_id` | integer | yes | The conversation that stays. |

Uses the Merge action of FreeScout, which its REST API does not offer. conversation_id is merged into merge_into_id, and the response names the conversation that remains. Do it for two conversations of the same customer; merging customers is a different action. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "merged_conversation_id": 4833,
  "remaining_conversation_id": 4821,
  "url": "https://support.yourcompany.com/conversation/4821"
}
```

## How do I connect FreeScout to Claude Code, Codex or Cursor?

Connecting FreeScout takes three steps: sign up, sign in to FreeScout 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 FreeScout to your agent.

1. **Create an account** Sign up and add FreeScout in the console. Your API key is there too.

2. **Sign in to FreeScout in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to FreeScout 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 FreeScout 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 active conversations in my Support mailbox where the customer wrote last. Read the thread and any notes, and save a draft reply for each one you can answer. Leave refunds and legal questions for me.
```

### Call FreeScout 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/freescout 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 PUT https://cotlet.dev/api/v1/freescout/conversations/4790/status \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status":"closed"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "conversation_id": 4790,
  "status": "closed",
  "changed_at": "2026-10-23T08:20:00Z"
}
```

## Why use Cotlet for FreeScout?

**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 FreeScout 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 FreeScout changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect FreeScout to Cotlet?

Yes. You sign in to FreeScout yourself, in your own Cloud Browser, and we never save your password. Your agents only get FreeScout 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 FreeScout integration?**

No, Cotlet is independent of FreeScout. FreeScout's own API is too limited for this work. Cotlet works through your own FreeScout account, the way you use FreeScout 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 FreeScout in your console: your agents lose access at once and you stay signed in. Signing out of FreeScout in the browser works too, and Reset browser deletes the whole profile.

## Is there a FreeScout MCP server on GitHub?

Yes. Community FreeScout MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, point it at your FreeScout with an API key, and keep it running yourself; when FreeScout or its API changes, it can stop working until you or the maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Install the server, enable API access on your FreeScout, create a key, add it to each MCP client | Sign up, sign in to FreeScout once, add one MCP server or API key |
| When FreeScout changes | It can break until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your FreeScout access | An API key in a file or environment variable on your computer, readable by any program you run | Your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access ends | The key works until you revoke it | Your Cloud Browser keeps you signed in; if FreeScout 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 FreeScout 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 FreeScout API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the FreeScout 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 10 credits (about $0.04 to $0.06), 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 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. [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 FreeScout 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 FreeScout 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 FreeScout only after you enable it. When FreeScout 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 FreeScout, sign out of FreeScout 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.
- **FreeScout's terms:** You use your own FreeScout account and stay responsible for following FreeScout's terms. Cotlet is independent and not affiliated with FreeScout. [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 FreeScout in the console and press Request access. Then you create your API key and connect FreeScout there.

**Do I need to be technical?**

No. You sign in to FreeScout 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 FreeScout to Cotlet?**

Yes. You sign in to FreeScout yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get FreeScout 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 FreeScout 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 FreeScout 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 FreeScout's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. FreeScout 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 FreeScout 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?**

FreeScout 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).

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

**Can my agent post or send messages in FreeScout without asking me?**

No. Every call to add_note, reply_to_customer, assign_conversation, move_conversation or merge_conversations waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. set_conversation_status runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the FreeScout 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/freescout 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.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

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.