Kommo MCP: 152 tools for Kommo CRM
Kommo MCP Server
An MCP server with broad Kommo API v4 coverage: 152 tools, files, conversations, analytics, OAuth refresh and a ready Cursor skill
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- 152 tools cover writes to almost every Kommo entity, including webhooks and salesbots
- Auto-refreshing OAuth tokens are saved in a .kommo_tokens.json file
Install
Manual install
npm install && cp .env.example .env && npm run buildThen fill .env with your Kommo credentials.
This is third-party code. Review the repository files before installing.
What it does
The server wraps nearly the entire Kommo API v4: leads, contacts, companies, pipelines and stages, tasks, notes, tags, custom fields, catalogs, users and roles, events, links and unsorted leads, plus automation and messaging: webhooks, salesbots, conversations and messages, calls, sources, chat templates and widgets. There is also a Files API with chunked uploads and entity attachment, and analytics: a dashboard, a sales report, pipeline analytics. The author explicitly compares the project with three other open Kommo servers and says it borrowed their best practices, OAuth token persistence, HAL response normalization, HTTP deployment and fast analytics shortcuts, while keeping the broadest API coverage. A Cursor skill ships alongside it, installed with a separate command, that teaches the agent how to configure and use this specific server.
Who it is for. For teams that need the fullest possible access to the Kommo API from one server: not just CRM entities, but files, conversations, analytics and automation.
Good fit when
- You need the broadest possible Kommo API v4 coverage in one server, including files, conversations and analytics
- You want OAuth with token refresh, not just a long-lived token
- You work in Cursor and want a ready skill on top of the server via npx skills add
Not a fit when
- You want a small server with a dozen basic tools, not 152 at once
- Your CRM is the Russian amoCRM, not the international Kommo
Example request
Build a quarterly sales report and show pipeline analytics by stageLimitations
Kommo is an international product, separate from the Russian amoCRM since 2022. Such broad API coverage means a larger surface for configuration mistakes and more integration privileges than a narrow task needs; it is worth granting the token only the scopes required. The client hard-limits requests to 7 per second, which can be slow for large batch operations.
How to disable. Remove the kommo server from your Cursor config, or stop the Docker container if it runs in HTTP mode.
MCP
- Transport
- stdio, http
- Authentication
- OAuth
| Environment variables | |
|---|---|
| KOMMO_SUBDOMAIN required | Kommo account subdomain |
| KOMMO_ACCESS_TOKEN secret | Long-lived token, an alternative to the OAuth trio |
| KOMMO_CLIENT_ID | Client ID for OAuth authorization with refresh |
| MCP_TRANSPORT | stdio by default, or http for Streamable HTTP on 127.0.0.1:3000 |
Security check
- 152 tools cover writes to almost every Kommo entity, including webhooks and salesbots
- Auto-refreshing OAuth tokens are saved in a .kommo_tokens.json file
README in short
The README openly compares the project to three other community Kommo servers and lists the practices it borrowed, gives a table of all environment variables, npm install and npm run build commands, stdio and HTTP launch modes, a Cursor config example, a separate command to install the companion skill via npx skills add, and links to the official Kommo docs on tokens and OAuth.
FAQ
How is this different from other open Kommo servers?
The README explicitly compares it to Miguelgbastos/Kommo-MCP, ampulex-23/KommoMCP and cAIborg-ai/amocrm-mcp and claims the broadest API coverage while keeping their best practices.
Can it connect over HTTP instead of just stdio?
Yes, the MCP_TRANSPORT=http variable switches the server to Streamable HTTP on 127.0.0.1:3000 with /mcp and /health endpoints.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
Yandex Kit skills for store management
kit-skills
Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex
YouGile MCP by Indalo
YouGile MCP
Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit
Bitrix24 portal MCP server
MCP-сервер портала Битрикс24
Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail