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

# Chatwoot API and MCP server

> Chatwoot has a full REST API, the Application API, and an official command-line client, but no official MCP server (checked 22 Oct 2026). The API covers conversations, messages, contacts, labels, teams and assignments with an access token from Profile Settings. Captain custom tools only call your own HTTPS endpoints, and Chatwoot's help center does not mention MCP.

Open-source customer support platform: email, live chat, WhatsApp and social messages land in one shared inbox, where agents assign, label, reply to and resolve conversations.

## What is the Chatwoot API?

Cotlet's Chatwoot API exposes 14 endpoints for your own Chatwoot account: list conversations, get conversation, search contacts, list inboxes, list agents, list teams, list labels, list canned responses, send reply, add private note, assign conversation, set conversation status, add labels and set priority. The list_conversations endpoint returns conversations of your account with status, assignee, labels, priority and the last message. Each endpoint takes simple JSON inputs like conversation_id, status or query and works both as an operation of the chatwoot_read or chatwoot_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Customer support](https://cotlet.dev/integrations/category/customer-support.md)
- **Endpoints:** 14 (8 read, 6 write)
- **Updated:** 2026-10-16

Chatwoot has a full REST API, the Application API, and an official command-line client, but no official MCP server (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Chatwoot with 14 endpoints (8 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Chatwoot have an official API?

Chatwoot has a full REST API, the Application API, and an official command-line client, but no official MCP server (checked 22 Oct 2026). The API covers conversations, messages, contacts, labels, teams and assignments with an access token from Profile Settings. Captain custom tools only call your own HTTPS endpoints, and Chatwoot's help center does not mention MCP.

| Task | Chatwoot official | Cotlet |
|---|---|---|
| List and filter conversations | Yes: Application API; you create the token and handle paging | Yes |
| Read a conversation with its messages | Yes: Application API | Yes |
| Reply to the customer | Yes: Application API; no MCP server for agents | Yes |
| Add a private note | Yes: Application API, message marked private | Yes |
| Assign an agent or a team | Yes: Application API | Yes |
| Resolve, snooze or reopen | Yes: Application API, toggle status | Yes |
| Add labels and set priority | Yes: Application API; the labels call overwrites the list | Yes |
| Work from an AI agent without a token or code | No: No official MCP server; the official CLI runs on your computer with your token | Yes |

Sources: [Chatwoot developers: Introduction to Chatwoot APIs](https://developers.chatwoot.com/api-reference/introduction), [Chatwoot developers: Chatwoot CLI](https://developers.chatwoot.com/cli), [Chatwoot Help: How to find your personal access token](https://chatwoot.help/hc/user-guide/articles/1757445004-how-to-find-your-personal-access-token-in-chatwoot), [Chatwoot Help: Captain articles, including custom tools](https://chatwoot.help/hc/user-guide/en/categories/captain)

## For AI agents

```text
Chatwoot has a full REST API, the Application API, and an official command-line client, but no official MCP server (checked 22 Oct 2026). The API covers conversations, messages, contacts, labels, teams and assignments with an access token from Profile Settings. Captain custom tools only call your own HTTPS endpoints, and Chatwoot's help center does not mention MCP.
Cotlet provides a hosted MCP server and REST API for Chatwoot: 14 tools (8 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=chatwoot, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    chatwoot_read, chatwoot_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/chatwoot, each operation at its own route, e.g. POST /api/v1/chatwoot/conversations/{conversation_id}/assign
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_conversations, get_conversation, search_contacts, list_inboxes, list_agents, list_teams, list_labels, list_canned_responses, send_reply, add_private_note, assign_conversation, set_conversation_status, add_labels, set_priority
Confirm      send_reply, add_private_note (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/chatwoot-api-mcp-server.md

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

## What can an AI agent do in Chatwoot?

Cotlet is best for Chatwoot admins and support leads who want their AI agent to triage, label, assign and reply to conversations without running or fixing a server.

- **[Triage new conversations](https://cotlet.dev/integrations/chatwoot-api-mcp-server/triage-new-conversations.md)** (runs: daily): "Go through unassigned open Chatwoot conversations. Add the label that fits (billing, bug or how-to), set the priority from what the customer wrote, assign billing to the Billing team, and leave a one-line private note with the reason. Leave unclear ones for me." → `list_conversations`, `get_conversation`, `list_labels`, `list_teams`, `add_labels`, `set_priority`, `assign_conversation`, `add_private_note`
- **[Reply to common questions from canned responses](https://cotlet.dev/integrations/chatwoot-api-mcp-server/reply-from-canned-responses.md)** (runs: daily): "Find open Chatwoot conversations where the customer wrote last and the question matches one of my canned responses. Send that response with the customer's first name filled in. If nothing fits, leave the conversation for me." → `list_canned_responses`, `list_conversations`, `get_conversation`, `send_reply`
- **[Snooze or resolve stale conversations](https://cotlet.dev/integrations/chatwoot-api-mcp-server/resolve-stale-conversations.md)** (runs: weekly): "List Chatwoot conversations in pending or open with no activity for 7 days. Resolve the ones where the customer confirmed the fix, snooze the ones waiting on a date, and leave a private note on each saying why. Do not touch conversations where the customer wrote last." → `list_conversations`, `get_conversation`, `add_private_note`, `set_conversation_status`
- **Daily digest of unassigned conversations** (runs: daily): "Every morning, count the unassigned open Chatwoot conversations per inbox and list the three that have waited longest." → `list_inboxes`, `list_conversations`
- **Pull a customer's history before replying**: "Find the contact for priya@example.com and summarize their earlier Chatwoot conversations in five lines before I reply." → `search_contacts`, `list_conversations`, `get_conversation`

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

Yes. Cotlet does not replace your automation platform: it gives it a Chatwoot 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 conversations, 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/chatwoot/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/chatwoot/conversations with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 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 Chatwoot.

### list_conversations

Conversations of your account with status, assignee, labels, priority and the last message. Access: read. REST: `GET /api/v1/chatwoot/conversations`. MCP: `chatwoot_read → list_conversations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | open, pending, resolved, snoozed or all. Default: open. |
| `assignee` | string | no | me, unassigned, assigned or all. Default: all. |
| `inbox_id` | integer | no | inbox_id from list_inboxes. |
| `label` | string | no | Label name from list_labels. |
| `contact_id` | integer | no | contact_id from search_contacts, for the conversations of one contact. |
| `query` | string | no | Text to find in the messages. |
| `page` | integer | no | Page number, from 1. Default: 1. |

Returns one page of conversations, most recent activity first, with status, priority, inbox, channel, contact, assignee, labels, unread_count, last_message and last_activity_at. status picks the Chatwoot state: open, pending, resolved, snoozed or all. assignee is me, unassigned, assigned or all. query matches the text of messages. Pass page back for the next one and stop when has_more is false.

Example response:

```json
{
  "conversations": [
    {
      "conversation_id": 1842,
      "status": "open",
      "priority": null,
      "inbox": "Support email",
      "channel": "email",
      "contact": {
        "contact_id": 311,
        "name": "Dana Whitfield"
      },
      "assignee": null,
      "labels": [],
      "unread_count": 2,
      "last_message": {
        "sender": "contact",
        "content": "I was charged twice for October. Can you refund one payment?",
        "created_at": "2026-10-22T06:41:00Z"
      },
      "last_activity_at": "2026-10-22T06:41:00Z"
    },
    {
      "conversation_id": 1851,
      "status": "open",
      "priority": null,
      "inbox": "Website chat",
      "channel": "web_widget",
      "contact": {
        "contact_id": 327,
        "name": "Priya Nair"
      },
      "assignee": null,
      "labels": [],
      "unread_count": 1,
      "last_message": {
        "sender": "contact",
        "content": "I cannot find where to reset my password.",
        "created_at": "2026-10-22T07:12:00Z"
      },
      "last_activity_at": "2026-10-22T07:12:00Z"
    }
  ],
  "page": 1,
  "has_more": false
}
```

### get_conversation

One conversation with its contact, assignee, labels and every message, private notes included. Access: read. REST: `GET /api/v1/chatwoot/conversations/{conversation_id}`. MCP: `chatwoot_read → get_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | conversation_id from list_conversations. It is the number in the conversation URL. |

Returns the conversation and its messages in time order. Each message has a sender (contact, agent or bot), a private flag and its text. Private notes are marked private: true and are never seen by the customer. Attachments appear as names, not files. Your role decides which conversations open; a conversation outside your inboxes returns APP_PERMISSION_DENIED.

Example response:

```json
{
  "conversation_id": 1842,
  "status": "open",
  "priority": null,
  "inbox": "Support email",
  "contact": {
    "contact_id": 311,
    "name": "Dana Whitfield",
    "email": "dana.whitfield@example.com"
  },
  "assignee": null,
  "team": null,
  "labels": [],
  "messages": [
    {
      "message_id": 90377,
      "sender": "contact",
      "private": false,
      "content": "I was charged twice for October. Can you refund one payment?",
      "created_at": "2026-10-22T06:41:00Z"
    }
  ]
}
```

### search_contacts

Find contacts by a search term, with their email, phone and number of conversations. Access: read. REST: `GET /api/v1/chatwoot/contacts/search`. MCP: `chatwoot_read → search_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Text to search for, for example an email address. |
| `page` | integer | no | Page number, from 1. Default: 1. |

Returns the contacts that match the term, with contact_id, name, email, phone and conversation count. Use contact_id as the contact_id of list_conversations to read their history. Chatwoot lists only resolved contacts, the ones with an identifier, an email or a phone number.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": 327,
      "name": "Priya Nair",
      "email": "priya@example.com",
      "phone": null,
      "conversations": 3
    }
  ],
  "page": 1,
  "has_more": false
}
```

### list_inboxes

Inboxes of your account with their name and channel type. Access: read. REST: `GET /api/v1/chatwoot/inboxes`. MCP: `chatwoot_read → list_inboxes`.

No parameters.

Returns every inbox you can see, with inbox_id, name and channel (email, web_widget, whatsapp and so on). Use inbox_id as the inbox_id of list_conversations. An agent sees only the inboxes it belongs to.

Example response:

```json
{
  "inboxes": [
    {
      "inbox_id": 2,
      "name": "Support email",
      "channel": "email"
    },
    {
      "inbox_id": 3,
      "name": "Website chat",
      "channel": "web_widget"
    }
  ]
}
```

### list_agents

Agents of your account with name, email, role and availability. Access: read. REST: `GET /api/v1/chatwoot/agents`. MCP: `chatwoot_read → list_agents`.

No parameters.

Returns the agents and administrators of the account with agent_id, name, email, role and availability. Use agent_id as the agent_id of assign_conversation. Availability is what Chatwoot shows for the agent right now.

Example response:

```json
{
  "agents": [
    {
      "agent_id": 7,
      "name": "Maya Brandt",
      "email": "maya@example.com",
      "role": "administrator",
      "availability": "online"
    },
    {
      "agent_id": 9,
      "name": "Jon Reyes",
      "email": "jon@example.com",
      "role": "agent",
      "availability": "offline"
    }
  ]
}
```

### list_teams

Teams of your account with their id and description. Access: read. REST: `GET /api/v1/chatwoot/teams`. MCP: `chatwoot_read → list_teams`.

No parameters.

Returns every team with team_id, name and description. Use team_id as the team_id of assign_conversation. Teams are created in Settings by an administrator.

Example response:

```json
{
  "teams": [
    {
      "team_id": 4,
      "name": "Billing",
      "description": "Payments, invoices and refunds"
    },
    {
      "team_id": 5,
      "name": "Tier 2",
      "description": "Bugs and account problems"
    }
  ]
}
```

### list_labels

Labels of your account with their description. Access: read. REST: `GET /api/v1/chatwoot/labels`. MCP: `chatwoot_read → list_labels`.

No parameters.

Returns every label with its title and description. Labels are account-specific and are created in Settings > Labels, so add_labels uses only names from this list. Label names hold letters, numbers, hyphens and underscores.

Example response:

```json
{
  "labels": [
    {
      "title": "billing",
      "description": "Payment and invoice questions"
    },
    {
      "title": "refund",
      "description": "Customer asks for money back"
    },
    {
      "title": "bug",
      "description": "Something does not work"
    }
  ]
}
```

### list_canned_responses

Canned responses of your account with short code and content. Access: read. REST: `GET /api/v1/chatwoot/canned-responses`. MCP: `chatwoot_read → list_canned_responses`.

No parameters.

Returns every canned response with its short_code and content. Variables such as {{contact.first_name}} stay in the content as written, and the agent fills them in before send_reply. Canned responses are shared by all agents of the account.

Example response:

```json
{
  "canned_responses": [
    {
      "short_code": "reset-password",
      "content": "Hi {{contact.first_name}}, you can reset your password from the sign-in page: choose Forgot your password and follow the link in the email."
    },
    {
      "short_code": "refund-policy",
      "content": "Hi {{contact.first_name}}, refunds are handled by our billing team within a few business days."
    }
  ]
}
```

### send_reply

Send a public reply to the customer in a conversation. Access: write, asks the user first. REST: `POST /api/v1/chatwoot/conversations/{conversation_id}/replies`. MCP: `chatwoot_write → send_reply`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | conversation_id from list_conversations. It is the number in the conversation URL. |
| `body` | string | yes | Reply text. |

Sends a message that the customer sees, through the channel of the conversation's inbox, under your agent name. The text goes out as written, with no variables filled in. A sent reply cannot be unsent through Cotlet. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "message_id": 90412,
  "conversation_id": 1851,
  "private": false,
  "status": "sent",
  "created_at": "2026-10-22T07:20:00Z"
}
```

### add_private_note

Add a private note that only your team sees. Access: write, asks the user first. REST: `POST /api/v1/chatwoot/conversations/{conversation_id}/private-notes`. MCP: `chatwoot_write → add_private_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | conversation_id from list_conversations. It is the number in the conversation URL. |
| `body` | string | yes | Note text. |

Adds a note to the conversation that the customer is never notified about; your teammates see it in the thread. A note cannot be removed through Cotlet. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "message_id": 90413,
  "conversation_id": 1842,
  "private": true,
  "created_at": "2026-10-22T07:21:00Z"
}
```

### assign_conversation

Assign a conversation to an agent or a team, or remove its assignee. Access: write. REST: `POST /api/v1/chatwoot/conversations/{conversation_id}/assign`. MCP: `chatwoot_write → assign_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | conversation_id from list_conversations. It is the number in the conversation URL. |
| `agent_id` | integer | no | agent_id from list_agents. |
| `team_id` | integer | no | team_id from list_teams. |
| `unassign` | boolean | no | true removes the assignee. |

Sets the Assignee, the Team or both. Pass agent_id from list_agents, team_id from list_teams, or unassign true to remove the assignee. Assigning does not change the status. assign_conversation runs without asking first: it reaches no customer and is undone with one call.

Example response:

```json
{
  "conversation_id": 1842,
  "assignee": null,
  "team": {
    "team_id": 4,
    "name": "Billing"
  }
}
```

### set_conversation_status

Open, pend, resolve or snooze a conversation. Access: write. REST: `PUT /api/v1/chatwoot/conversations/{conversation_id}/status`. MCP: `chatwoot_write → set_conversation_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | conversation_id from list_conversations. It is the number in the conversation URL. |
| `status` | string | yes | open, pending, resolved or snoozed. |
| `snoozed_until` | string | no | ISO 8601 time to reopen, only with status snoozed. |

Sets the status to open, pending, resolved or snoozed. A snooze without snoozed_until lasts until the customer writes again, and a reply from the customer always reopens a snoozed conversation. Automation rules on Conversation updated or Conversation opened run as they do for a person. set_conversation_status runs without asking first: it sends nothing to the customer and is undone with one call.

Example response:

```json
{
  "conversation_id": 1790,
  "status": "snoozed",
  "snoozed_until": "2026-11-02T09:00:00Z"
}
```

### add_labels

Add labels to a conversation and keep the ones it has. Access: write. REST: `POST /api/v1/chatwoot/conversations/{conversation_id}/labels`. MCP: `chatwoot_write → add_labels`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | conversation_id from list_conversations. It is the number in the conversation URL. |
| `labels` | string[] | yes | Label names from list_labels. |

Adds the labels you pass to the existing ones and returns the full list. A name that is not in list_labels fails and nothing is changed. Labels are account-specific and are not created by this tool. add_labels runs without asking first: it reaches no customer and is undone with one call.

Example response:

```json
{
  "conversation_id": 1842,
  "labels": [
    "billing",
    "refund"
  ],
  "added": [
    "billing",
    "refund"
  ]
}
```

### set_priority

Set the priority of a conversation, or clear it. Access: write. REST: `PUT /api/v1/chatwoot/conversations/{conversation_id}/priority`. MCP: `chatwoot_write → set_priority`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | conversation_id from list_conversations. It is the number in the conversation URL. |
| `priority` | string | yes | urgent, high, medium, low or none. |

Sets one of Chatwoot's four fixed priorities, or none to clear it. Chatwoot has no custom priorities; use labels for finer sorting. The priority shows in the conversation list and adds an activity entry in the thread. set_priority runs without asking first: it reaches no customer and is undone with one call.

Example response:

```json
{
  "conversation_id": 1842,
  "priority": "high"
}
```

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

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

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

2. **Sign in to Chatwoot in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Chatwoot 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 Chatwoot 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 unassigned open Chatwoot conversations. Add the label that fits (billing, bug or how-to), set the priority from what the customer wrote, assign billing to the Billing team, and leave a one-line private note with the reason. Leave unclear ones for me.
```

### Call Chatwoot 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/chatwoot 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 POST https://cotlet.dev/api/v1/chatwoot/conversations/1842/assign \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"team_id":4}'
```

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

```
{
  "conversation_id": 1842,
  "assignee": null,
  "team": {
    "team_id": 4,
    "name": "Billing"
  }
}
```

## Why use Cotlet for Chatwoot?

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

## Is it safe to connect Chatwoot to Cotlet?

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

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

## Is there a Chatwoot MCP server on GitHub?

Yes. Several community Chatwoot MCP servers exist on GitHub, usually maintained by one person. You install one yourself, give it an API access token, and fix it when Chatwoot changes its API. Cotlet hosts the same kind of server for you, signs in as your own agent user, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, create an access token in Profile Settings, store it, add the server to each MCP client | Sign up, sign in to Chatwoot once, add one MCP server or API key |
| When Chatwoot changes | It breaks until you or the maintainer fix it; Chatwoot says the api_access_token header is slated for deprecation in favor of Bearer tokens | Our team tests it daily and fixes it for you; failed calls are free |
| Your Chatwoot access | An access token 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 create a new token and paste it in by hand | Your Cloud Browser keeps you signed in; if Chatwoot 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 Chatwoot 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 Chatwoot API cost?

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

**Do I need to be technical?**

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

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

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

**Does my agent need a Chatwoot API access token?**

No. Cotlet works in your own signed-in Chatwoot, so you create no token. Chatwoot shows the token in Profile Settings and, per its help center, only with administrator privileges. What your agent can do follows your role: Chatwoot roles such as Manage All Conversations or Manage Unassigned & Own Conversations decide which conversations it sees, and a call outside that fails with APP_PERMISSION_DENIED.

**Why not use Captain's custom tools?**

Captain custom tools go the other way: Captain calls your own HTTPS endpoint to answer a customer. They are on the Business and Enterprise plans, and they do not let Claude Code, n8n or a script work in your inbox. Cotlet gives your own agent the inbox, the way an agent on your team would use it.

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

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

**Can I use the Chatwoot 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/chatwoot 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.