Invoicing & freelance CRM
Dubsado
Projects, proposals, contracts and invoices for creative businesses.
14 endpoints
Kommo has an API but no Kommo-hosted agent server, and its Chats API for messages is for Pro and Enterprise plans only. Sign in to Kommo once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.
Not affiliated with Kommo.
| What you need | Kommo's API | GitHub MCP server | Cotlet |
|---|---|---|---|
| MCP tools, chats, incoming leads | No | Partly | Yes, 15 tools |
| Acts as you, signed in 24/7 | No | No | Yes, Cloud Browser |
| Fixed for you when Kommo changes | N/A | No | Yes, tested every 6h |
| Runs with your laptop off | N/A | No | Yes, hosted |
Checked Oct 20, 2026. Sources: Kommo developers: API limitations · Kommo developers: Get leads · Kommo Help: Purchase Chats API messages add-on · Zapier: Kommo integrations
AI agents connect over MCP, scripts call the REST API. Both reach the same 15 tools with one API key.
Add Cotlet to your agent once. Kommo and every other app you connect show up as its tools.
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" {
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.
Every tool is an endpoint under /api/v1/kommo with its own method and path, such as POST /api/v1/kommo/pipelines/{pipeline_id}/leads, with the same API key. Our open-source repo has ready scripts to start from.
15 tools on your own Kommo account. Agents call them as operations of the MCP tools kommo_read and kommo_write; scripts call each one at its own REST endpoint, with the same inputs and answers.
| Tool | What it does | Access |
|---|---|---|
| list_pipelines | Pipelines of the account with their stages, in the order Kommo shows them. | read |
| list_leads | Leads from Pipelines → All leads, filtered by pipeline, stage, responsible user or overdue tasks. | read |
| get_lead | The lead card: fields, linked contact and company, tasks and notes. | read |
| list_incoming_leads | Chats waiting in the Incoming leads stage to be accepted, declined or linked. | read |
| list_tasks | Tasks from Calendar, filtered by lead, responsible user or status. | read |
| list_conversations | Conversations from Communication → Chat inbox, with the last message and whether it is unanswered. | read |
| get_conversation | The message history of one chat. | read |
| create_lead | Add a lead to a pipeline stage, optionally with a contact. | writeasks first |
| update_lead | Change the name, sale amount, responsible user or tags of a lead. | writeasks first |
| move_lead_stage | Move a lead to another stage, in any pipeline, or close it as Won or Lost. | writeasks first |
| create_task | Add a task to a lead with a deadline, a responsible user and a comment. | writeasks first |
| add_note | Add a text note to the lead card. | writeasks first |
| send_message | Reply in a chat of the Chat inbox. | writeasks first |
| accept_incoming_lead | Turn an incoming chat into a lead, the Accept button in the chat. | writeasks first |
| decline_incoming_lead | Reject an incoming chat as spam, the Decline button in the chat. | writeasks first |
Scroll the table for all 15 tools.
You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.
One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Kommo is enabled for agents, so 20 calls a day come to 550 credits.
| 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.
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.
Sign up free, open Kommo under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.
No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 15 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.
Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Kommo yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Kommo sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.
Not on anything that reaches other people: create_lead, update_lead, move_lead_stage, create_task, add_note, send_message, accept_incoming_lead, decline_incoming_lead wait for your OK by default. You can switch that off per tool for scheduled runs.
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.
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.
Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Kommo changes. Pick Cotlet if you want it hosted and kept working for you.
Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.
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.
No. Cotlet is independent and not affiliated with Kommo.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy