Kommo MCP server
14 operations0 webhooks
CRM with Kommo - manage leads, contacts, companies and tasks, and read the pipelines with their stages, the account users and the account itself.
Try Kommo with your agent
Connect Kommo, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in Kommo on my account, then run one read-only example and show me the result.
Kommo tools and triggers
Tools are what your agent can do in Kommo through Corsair's MCP server. Triggers are the Kommo events a routine can start from.
Contacts
- CreateWrite
Create contacts, each with a name or a first and last name, and custom fields
contacts.create
- GetRead-only
One contact with its custom field values
contacts.get
- ListRead-only
Contacts by owner or update date, paged, optionally with their leads
contacts.list
- UpdateWrite
Change fields on one or more contacts, each named by its `id`
contacts.update
Leads
- CreateWrite
Create up to 250 leads in one request, each with its price, stage, pipeline and custom fields
leads.create
- GetRead-only
One lead with its custom field values and, on request, its contacts, loss reason and source
leads.get
- ListRead-only
Leads by pipeline, stage, owner or date, paged 250 at a time; `next_page` says whether another exists
leads.list
- UpdateWrite
Change fields on one or more leads, each named by its `id`; a field left out is untouched
leads.update
Tasks
- CreateWrite
Create tasks against a lead, contact or company; every task needs a `complete_till` deadline
tasks.create
- ListRead-only
Tasks by entity, owner or completion, paged; the deadline is a Unix timestamp
tasks.list
Account
- GetRead-only
The account itself: its name, subdomain, currency and country
account.get
Companies
- ListRead-only
Companies by owner or update date, paged
companies.list
Pipelines
- ListRead-only
The lead pipelines with their stages, which is where a lead’s `pipeline_id` and `status_id` come from
pipelines.list
Users
- ListRead-only
The account’s users, for looking up a responsible user ID
users.list
Connect Kommo to Claude, ChatGPT or Cursor
- 1
Connect Kommo in Corsair
Add your Kommo API key once in Corsair. Corsair stores the credential encrypted and makes the Kommo API calls for your agent, so it never goes into a prompt or a config file. Connect Kommo
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Kommo. On a ChatGPT personal plan, connect Kommo here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. None of Kommo's operations are destructive, so in the default Cautious mode they all run right away. Strict mode asks before each of its 5 writes, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/kommo, add the Kommo plugin, and connect with an API key. Then call methods like corsair.kommo.api.account.get() from your app. Corsair keeps each tenant isolated.
Yes. Kommo requires an API key from your Kommo account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Kommo, GitHub, Notion, Stripe, and the rest. Trigger Kommo from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for CRM with Kommo - manage leads, contacts, companies and tasks, and read the pipelines with their stages, the account users and the account itself. Common builds include sync jobs, admin tooling, and agents that call Kommo APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Kommo API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/kommo in the open repo. When Kommo ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Kommo data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Kommo data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put Kommo on a link in Strict mode and every write waits for your approval, while destructive actions are refused. None of the Kommo operations are destructive, so the default Cautious mode runs them all without asking. You can change a link's mode at hub.corsair.dev/me.