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

# Kommo API and MCP server

> Kommo has a full REST API, but no Kommo-hosted MCP server in its docs (checked 20 Oct 2026). The API signs in with OAuth 2.0 or a long-lived token and allows 7 requests per second. Its Chats API for messages is for Pro and Enterprise plans only.

CRM for selling in messengers: chats from WhatsApp, Instagram and other channels become leads that move through pipelines, with tasks, a Chat inbox and automation in Digital Pipeline.

## What is the Kommo API?

Cotlet's Kommo API exposes 15 endpoints for your own Kommo account: list pipelines and stages, list leads, get a lead, list incoming leads, list tasks, list chat conversations, get a conversation, create a lead, update a lead, move a lead to a stage, create a task, add a note to a lead, send a chat message, accept an incoming lead and decline an incoming lead. The list_pipelines endpoint returns pipelines of the account with their stages, in the order Kommo shows them. Each endpoint takes simple JSON inputs like responsible_user_id, lead_id or cursor and works both as an operation of the kommo_read or kommo_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Invoicing & freelance CRM](https://cotlet.dev/integrations/category/invoicing-freelance-crm.md)
- **Endpoints:** 15 (7 read, 8 write)
- **Updated:** 2026-10-22

Kommo has a full REST API, but no Kommo-hosted MCP server in its docs (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for Kommo with 15 endpoints (7 read, 8 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Kommo have an official API?

Kommo has a full REST API, but no Kommo-hosted MCP server in its docs (checked 20 Oct 2026). The API signs in with OAuth 2.0 or a long-lived token and allows 7 requests per second. Its Chats API for messages is for Pro and Enterprise plans only.

| Task | Kommo official | Cotlet |
|---|---|---|
| List and read leads with filters | Yes: REST API, filters by pipeline, stage and responsible user; you build auth and paging yourself | Yes |
| Create and update leads, tags and responsible user | Yes: REST API; no MCP server for agents | Yes |
| Move a lead to another stage | Yes: REST API; no MCP server for agents | Yes |
| Create tasks on a lead | Yes: REST API, also a Zapier action | Yes |
| Read chat history | Partly: Chats API, Pro and Enterprise only | Yes |
| Reply in a chat | Partly: Chats API, Pro and Enterprise only; each sent message uses a message balance | Yes |

Sources: [Kommo developers: API limitations](https://developers.kommo.com/docs/limitations), [Kommo developers: Get leads](https://developers.kommo.com/reference/leads-list), [Kommo Help: Purchase Chats API messages add-on](https://support.kommo.com/docs/chats-api), [Zapier: Kommo integrations](https://zapier.com/apps/kommo/integrations)

## For AI agents

```text
Kommo has a full REST API, but no Kommo-hosted MCP server in its docs (checked 20 Oct 2026). The API signs in with OAuth 2.0 or a long-lived token and allows 7 requests per second. Its Chats API for messages is for Pro and Enterprise plans only.
Cotlet provides a hosted MCP server and REST API for Kommo: 15 tools (7 read, 8 write).
Access       Sign up at https://cotlet.dev/app/signup?app=kommo, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    kommo_read, kommo_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/kommo, each operation at its own route, e.g. POST /api/v1/kommo/pipelines/{pipeline_id}/leads
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_pipelines, list_leads, get_lead, list_incoming_leads, list_tasks, list_conversations, get_conversation, create_lead, update_lead, move_lead_stage, create_task, add_note, send_message, accept_incoming_lead, decline_incoming_lead
Confirm      create_lead, update_lead, move_lead_stage, create_task, add_note, send_message, accept_incoming_lead, decline_incoming_lead (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/kommo-api-mcp-server.md

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

## What can an AI agent do in Kommo?

Cotlet is best for Kommo admins and sales managers who want an AI agent to handle incoming leads, follow-up tasks and unanswered chats without running or fixing a server.

- **[Triage incoming leads](https://cotlet.dev/integrations/kommo-api-mcp-server/triage-incoming-leads.md)** (runs: daily): "Go through the incoming leads in Kommo. Accept real enquiries about our services and assign them to Anna, decline obvious spam, and leave the unclear ones for me with a one-line reason." → `list_incoming_leads`, `get_conversation`, `accept_incoming_lead`, `decline_incoming_lead`
- **[Create follow-up tasks for stale leads](https://cotlet.dev/integrations/kommo-api-mcp-server/chase-stale-leads-with-follow-up-tasks.md)** (runs: daily): "Find leads in the Proposal stage of the Sales pipeline that have no open task or an overdue one. Create a Follow-up task for each, due in 2 days, assigned to the lead owner, with a comment that says what to ask." → `list_leads`, `list_tasks`, `get_lead`, `create_task`
- **[Reply to unanswered chats](https://cotlet.dev/integrations/kommo-api-mcp-server/reply-to-unanswered-chats.md)** (runs: daily): "Find Kommo chats where the client wrote last and nobody has answered. Reply to the simple questions about opening hours and prices using the lead details, and list the rest for me." → `list_conversations`, `get_conversation`, `get_lead`, `send_message`
- **Move leads after a call** (runs: daily): "For the leads I talked to today, move each one to the stage that fits my call notes, add the tag "hot" to those who asked for a quote, and mark as Lost any who said no." → `list_leads`, `get_lead`, `move_lead_stage`, `update_lead`, `add_note`
- **Reassign and tag leads in bulk** (runs: weekly): "List leads with no responsible user, assign them to the manager with the fewest open leads and tag them "unassigned-fixed"." → `list_leads`, `update_lead`
- **Weekly pipeline digest** (runs: weekly): "Every Monday, list the leads in each stage of the Sales pipeline with their sale amount and flag those with an overdue task." → `list_pipelines`, `list_leads`, `list_tasks`

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

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

## Tools

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

### list_pipelines

Pipelines of the account with their stages, in the order Kommo shows them. Access: read. REST: `GET /api/v1/kommo/pipelines`. MCP: `kommo_read → list_pipelines`.

No parameters.

Returns each pipeline with its stage_id and stage name, in board order, plus the Won and Lost closing stages. Run it first: the other tools take pipeline_id and stage_id from it. Pipelines and stages you cannot see with your Kommo permissions are not returned.

Example response:

```json
{
  "pipelines": [
    {
      "pipeline_id": 8210123,
      "name": "Sales",
      "stages": [
        {
          "stage_id": 71000001,
          "name": "Incoming leads"
        },
        {
          "stage_id": 71000002,
          "name": "Contacted"
        },
        {
          "stage_id": 71000003,
          "name": "Proposal"
        },
        {
          "stage_id": 71000004,
          "name": "Negotiation"
        }
      ]
    }
  ]
}
```

### list_leads

Leads from Pipelines → All leads, filtered by pipeline, stage, responsible user or overdue tasks. Access: read. REST: `GET /api/v1/kommo/leads`. MCP: `kommo_read → list_leads`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `pipeline_id` | integer | no | Pipeline ID from list_pipelines. |
| `stage_id` | integer | no | Stage ID from list_pipelines; needs pipeline_id. |
| `responsible_user_id` | integer | no | Only leads of this user. |
| `overdue_tasks_only` | boolean | no | Only leads with an overdue task, the preset filter in the app. |
| `query` | string | no | Search text for the lead name and contact. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns leads in the order Kommo shows them, with name, stage, sale amount, responsible user, tags and the due date of the closest task (null when the lead has no open task). Closed leads (Won and Lost) are not in the pipeline view, so they are not listed. Follow next_cursor until it is null.

Example response:

```json
{
  "leads": [
    {
      "lead_id": 24518301,
      "name": "Yoga studio booking",
      "pipeline_id": 8210123,
      "stage": "Proposal",
      "sale": 750,
      "responsible": {
        "user_id": 9102334,
        "name": "Anna Berg"
      },
      "tags": [
        "website"
      ],
      "next_task_due": null,
      "created_at": "2026-10-08T09:14:00+02:00"
    },
    {
      "lead_id": 24518377,
      "name": "Cafe loyalty app",
      "pipeline_id": 8210123,
      "stage": "Proposal",
      "sale": 1900,
      "responsible": {
        "user_id": 9102334,
        "name": "Anna Berg"
      },
      "tags": [],
      "next_task_due": "2026-10-19T12:00:00+02:00",
      "created_at": "2026-10-05T16:40:00+02:00"
    }
  ],
  "next_cursor": null
}
```

### get_lead

The lead card: fields, linked contact and company, tasks and notes. Access: read. REST: `GET /api/v1/kommo/leads/{lead_id}`. MCP: `kommo_read → get_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `lead_id` | integer | yes | Lead ID from list_leads or get_lead. |

Returns what the lead card shows: stage, sale amount, responsible user, tags, the linked contact and company, open tasks and the latest notes, newest first. Use it before writing to a lead so the write fits what is already there. A lead you have no right to see returns APP_PERMISSION_DENIED.

Example response:

```json
{
  "lead_id": 24518301,
  "name": "Yoga studio booking",
  "stage": "Proposal",
  "sale": 750,
  "responsible": {
    "user_id": 9102334,
    "name": "Anna Berg"
  },
  "tags": [
    "website"
  ],
  "contact": {
    "contact_id": 1180442,
    "name": "Ana Lopez"
  },
  "company": {
    "company_id": 660201,
    "name": "Lotus Yoga"
  },
  "tasks": [],
  "notes": [
    {
      "text": "Sent proposal for 4 sessions a month.",
      "created_at": "2026-10-12T11:02:00+02:00"
    }
  ]
}
```

### list_incoming_leads

Chats waiting in the Incoming leads stage to be accepted, declined or linked. Access: read. REST: `GET /api/v1/kommo/incoming-leads`. MCP: `kommo_read → list_incoming_leads`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `pipeline_id` | integer | no | Only chats for this pipeline. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns chats that have not become leads yet, newest first, with the channel, the contact name, the first message and when it arrived. It works only when the Incoming leads stage is enabled for the pipeline; otherwise it returns an empty list. Follow next_cursor until it is null.

Example response:

```json
{
  "incoming": [
    {
      "chat_id": "c8f2a6d1",
      "channel": "WhatsApp",
      "contact_name": "Tom Becker",
      "first_message": "How much is a landing page for a dental clinic?",
      "received_at": "2026-10-20T07:41:00+02:00"
    },
    {
      "chat_id": "c1d7e9a3",
      "channel": "Instagram",
      "contact_name": "promo_deals_99",
      "first_message": "Earn 500 a day from home https://example.com/x",
      "received_at": "2026-10-20T06:12:00+02:00"
    }
  ],
  "next_cursor": null
}
```

### list_tasks

Tasks from Calendar, filtered by lead, responsible user or status. Access: read. REST: `GET /api/v1/kommo/tasks`. MCP: `kommo_read → list_tasks`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `lead_id` | integer | no | Only tasks of this lead. |
| `responsible_user_id` | integer | no | Only tasks of this user. |
| `status` | string | no | upcoming, overdue or completed. Default upcoming. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns tasks ordered by deadline, with type, comment, deadline, responsible user and the lead or contact each one is linked to. Follow next_cursor until it is null. Kommo tasks are linked to a lead or a contact, so a task with neither is not returned.

Example response:

```json
{
  "tasks": [
    {
      "task_id": 5530101,
      "lead_id": 24518377,
      "type": "Follow-up",
      "comment": "Ask about the loyalty app scope",
      "deadline": "2026-10-19T12:00:00+02:00",
      "responsible": {
        "user_id": 9102334,
        "name": "Anna Berg"
      },
      "status": "overdue"
    }
  ],
  "next_cursor": null
}
```

### list_conversations

Conversations from Communication → Chat inbox, with the last message and whether it is unanswered. Access: read. REST: `GET /api/v1/kommo/conversations`. MCP: `kommo_read → list_conversations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `unanswered_only` | boolean | no | Only chats where the client wrote last and nobody answered. |
| `responsible_user_id` | integer | no | Only chats of leads owned by this user. |
| `query` | string | no | Search text, the same as the Chat inbox search field. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns conversations newest first, with the channel, the contact, the linked lead_id (null if the chat is not a lead yet) and the last message with who wrote it: client, user or bot. A chat a Salesbot answered can still count as unanswered when the bot is set to leave messages unanswered. Follow next_cursor until it is null.

Example response:

```json
{
  "conversations": [
    {
      "chat_id": "c4b19e07",
      "channel": "WhatsApp",
      "contact_name": "Ana Lopez",
      "lead_id": 24518301,
      "unanswered": true,
      "last_message": {
        "from": "client",
        "text": "What does the yoga studio package cost per month?",
        "at": "2026-10-19T18:03:00+02:00"
      }
    }
  ],
  "next_cursor": null
}
```

### get_conversation

The message history of one chat. Access: read. REST: `GET /api/v1/kommo/chats/{chat_id}/conversation`. MCP: `kommo_read → get_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `chat_id` | string | yes | Chat ID from list_conversations or list_incoming_leads. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns messages newest first, each with who wrote it (client, user or bot), the text and the time. Images, voice messages and files come back as a type label without the content. Follow next_cursor for older messages.

Example response:

```json
{
  "chat_id": "c4b19e07",
  "channel": "WhatsApp",
  "lead_id": 24518301,
  "messages": [
    {
      "from": "client",
      "text": "What does the yoga studio package cost per month?",
      "at": "2026-10-19T18:03:00+02:00"
    },
    {
      "from": "user",
      "text": "Hi Ana, thanks for writing. I will send the details.",
      "at": "2026-10-19T09:30:00+02:00"
    }
  ],
  "next_cursor": null
}
```

### create_lead

Add a lead to a pipeline stage, optionally with a contact. Access: write, asks the user first. REST: `POST /api/v1/kommo/pipelines/{pipeline_id}/leads`. MCP: `kommo_write → create_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Lead name. |
| `pipeline_id` | integer | yes | Pipeline ID from list_pipelines. |
| `stage_id` | integer | no | Stage ID from list_pipelines. Default is the first stage. |
| `sale` | integer | no | Sale amount in the account currency. |
| `responsible_user_id` | integer | no | Owner of the lead. Default is you. |
| `tags` | array | no | Tag names to add. |
| `contact_name` | string | no | Creates and links a contact with this name. |

Creates the lead as the New lead button does and returns its lead_id and the card URL. A Digital Pipeline trigger on the stage fires for the new lead, so it can start a Salesbot or send an email. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "lead_id": 24519010,
  "name": "Dental clinic website",
  "pipeline_id": 8210123,
  "stage": "Contacted",
  "url": "https://yourcompany.kommo.com/leads/detail/24519010",
  "created_at": "2026-10-20T09:15:00+02:00"
}
```

### update_lead

Change the name, sale amount, responsible user or tags of a lead. Access: write, asks the user first. REST: `PATCH /api/v1/kommo/leads/{lead_id}`. MCP: `kommo_write → update_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `lead_id` | integer | yes | Lead ID from list_leads or get_lead. |
| `name` | string | no | New lead name. |
| `sale` | integer | no | New sale amount. |
| `responsible_user_id` | integer | no | New owner of the lead. |
| `add_tags` | array | no | Tag names to add. |
| `remove_tags` | array | no | Tag names to remove. |

Returns the lead as it is after the change. Only the fields you send change. Assigning a new responsible user can fire a Digital Pipeline trigger and the new owner sees the lead in their list. A tag that does not exist is created. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "lead_id": 24518301,
  "name": "Yoga studio booking",
  "sale": 750,
  "responsible": {
    "user_id": 9102334,
    "name": "Anna Berg"
  },
  "tags": [
    "website",
    "hot"
  ]
}
```

### move_lead_stage

Move a lead to another stage, in any pipeline, or close it as Won or Lost. Access: write, asks the user first. REST: `POST /api/v1/kommo/leads/{lead_id}/stage/move`. MCP: `kommo_write → move_lead_stage`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `lead_id` | integer | yes | Lead ID from list_leads or get_lead. |
| `stage_id` | integer | no | Target stage from list_pipelines. Leave out when you use close_as. |
| `close_as` | string | no | won or lost. Closes the lead the way dropping it on Won or Lost does. |

Returns the lead with its new stage. The expected revenue of the pipeline updates by itself. A Digital Pipeline trigger on the target stage fires, so it can send an email, start a Salesbot or add a task. A closed lead leaves the pipeline view. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "lead_id": 24518301,
  "from_stage": "Proposal",
  "to_stage": "Negotiation",
  "pipeline_id": 8210123
}
```

### create_task

Add a task to a lead with a deadline, a responsible user and a comment. Access: write, asks the user first. REST: `POST /api/v1/kommo/leads/{lead_id}/tasks`. MCP: `kommo_write → create_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `lead_id` | integer | yes | Lead ID from list_leads or get_lead. |
| `task_type` | string | no | Follow-up or Meeting, or the name of a custom type an admin added. Default Follow-up. |
| `deadline` | string | yes | ISO 8601 date and time. |
| `responsible_user_id` | integer | no | User the task is assigned to. Default is the lead owner. |
| `comment` | string | no | Task comment. |

Creates the task as Chat → Task → Set does on the lead card and returns its task_id. Kommo reminds the responsible user about the task, so it reaches a colleague. An unknown task_type fails and lists the types of the account. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "task_id": 5530194,
  "lead_id": 24518301,
  "type": "Follow-up",
  "deadline": "2026-10-22T10:00:00+02:00",
  "responsible": {
    "user_id": 9102334,
    "name": "Anna Berg"
  },
  "comment": "Proposal sent 12 Oct, no reply. Ask if the quote needs changes."
}
```

### add_note

Add a text note to the lead card. Access: write, asks the user first. REST: `POST /api/v1/kommo/leads/{lead_id}/notes`. MCP: `kommo_write → add_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `lead_id` | integer | yes | Lead ID from list_leads or get_lead. |
| `text` | string | yes | Note text. |

Adds the note to the activity feed of the lead and returns its note_id. Teammates who open the lead see it, and Cotlet cannot delete a note afterwards. Text only: it uploads no files. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "note_id": 77120044,
  "lead_id": 24518301,
  "text": "Call 20 Oct: wants 6 sessions a month, send a new quote.",
  "created_at": "2026-10-20T11:30:00+02:00"
}
```

### send_message

Reply in a chat of the Chat inbox. Access: write, asks the user first. REST: `POST /api/v1/kommo/chats/{chat_id}/messages`. MCP: `kommo_write → send_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `chat_id` | string | yes | Chat ID from list_conversations or list_incoming_leads. |
| `text` | string | yes | Message text. Plain text only. |

Sends the text in the same chat and channel, under your name, and returns the message_id. It reaches the client at once and Cotlet cannot recall it. Voice messages, files and templates are not sent. What the channel allows depends on the channel Kommo has connected. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "message_id": "m91d2c4",
  "chat_id": "c4b19e07",
  "status": "sent",
  "sent_at": "2026-10-20T09:20:00+02:00"
}
```

### accept_incoming_lead

Turn an incoming chat into a lead, the Accept button in the chat. Access: write, asks the user first. REST: `POST /api/v1/kommo/chats/{chat_id}/incoming-lead/accept`. MCP: `kommo_write → accept_incoming_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `chat_id` | string | yes | Chat ID from list_conversations or list_incoming_leads. |
| `responsible_user_id` | integer | no | Owner of the new lead. Default is you. |

Accepts the chat as the Accept button does: the lead is created and moves to the next stage. It returns the lead_id. A Digital Pipeline trigger on that stage fires for the new lead and can message the client. Chats that match an existing lead are not linked here. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "lead_id": 24519044,
  "chat_id": "c8f2a6d1",
  "stage": "Contacted",
  "responsible": {
    "user_id": 9102334,
    "name": "Anna Berg"
  }
}
```

### decline_incoming_lead

Reject an incoming chat as spam, the Decline button in the chat. Access: write, asks the user first. REST: `POST /api/v1/kommo/chats/{chat_id}/incoming-lead/decline`. MCP: `kommo_write → decline_incoming_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `chat_id` | string | yes | Chat ID from list_conversations or list_incoming_leads. |

Declines the chat as the Decline button does, which Kommo meant for spam, and returns its status. The chat leaves the Incoming leads queue and Cotlet has no call to bring it back. Nothing is sent to the sender. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "chat_id": "c1d7e9a3",
  "status": "declined"
}
```

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

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

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

2. **Sign in to Kommo in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Kommo 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 Kommo 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 incoming leads in Kommo. Accept real enquiries about our services and assign them to Anna, decline obvious spam, and leave the unclear ones for me with a one-line reason.
```

### Call Kommo 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/kommo 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/kommo/pipelines/8210123/leads \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Dental clinic website","stage_id":71000002,"sale":4800,"responsible_user_id":9102334,"tags":["website"],"contact_name":"Tom Becker"}'
```

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

```
{
  "lead_id": 24519010,
  "name": "Dental clinic website",
  "pipeline_id": 8210123,
  "stage": "Contacted",
  "url": "https://yourcompany.kommo.com/leads/detail/24519010",
  "created_at": "2026-10-20T09:15:00+02:00"
}
```

## Why use Cotlet for Kommo?

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

## Is it safe to connect Kommo to Cotlet?

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

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

## Is there a Kommo MCP server on GitHub?

Yes. Community Kommo MCP servers exist on GitHub, usually maintained by one person. You install one yourself, give it a Kommo access token, and fix it when Kommo changes. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, create a token or OAuth integration in Kommo, store it, add the server to each MCP client | Sign up, sign in to Kommo once, add one MCP server or API key |
| When Kommo 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 Kommo access | A token in a file or environment variable 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 renew the token or sign in again by hand | Your Cloud Browser keeps you signed in; if Kommo 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 Kommo 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 Kommo API cost?

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

**Do I need to be technical?**

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

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

Kommo 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 a Pro plan or the Chats API add-on?**

No. Cotlet works in your own signed-in Kommo, the way a seller does, and does not use the Chats API. Kommo limits that API to Pro and Enterprise plans and counts every message it sends against a monthly balance. Your role still counts: an Admin sets up the Chat inbox and adds task types, and a call without the right permission fails with APP_PERMISSION_DENIED.

**Will my Digital Pipeline triggers and Salesbots still run?**

Yes. They stay as you set them up under Leads → Automate. A lead your agent creates, accepts or moves enters a stage like any other, so a trigger on that stage can add a task, send an email or start a Salesbot. That is why each of those calls asks for your OK by default.

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

No. Every call to create_lead, update_lead, move_lead_stage, create_task, add_note, send_message, accept_incoming_lead or decline_incoming_lead 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 Kommo 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/kommo 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.