Kommo CRM MCP server and SDK
Kommo CRM MCP Server & SDK
A dual-purpose npm package: a 40-tool MCP server for Kommo CRM and a typed TypeScript SDK for the same operations in your own code
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
- Tools create and update leads, contacts, companies and catalogs in the CRM
- A long-lived access token in the config grants full access to the Kommo account
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/kommo-crm-mcp-server-sdkDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
This entry is high risk, so there is no one-click install. Review the code and add the config by hand.
Run in a terminal
claude mcp add --transport stdio --env 'KOMMO_SUBDOMAIN=<KOMMO_SUBDOMAIN value>' --env 'KOMMO_ACCESS_TOKEN=<your KOMMO_ACCESS_TOKEN>' kommo-crm -- npx -y @syncraengine/kommo-mcpOr add to the file .mcp.json, in the project
{
"mcpServers": {
"kommo-crm": {
"command": "npx",
"args": [
"-y",
"@syncraengine/kommo-mcp"
],
"env": {
"KOMMO_SUBDOMAIN": "<KOMMO_SUBDOMAIN value>",
"KOMMO_ACCESS_TOKEN": "<your KOMMO_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
KOMMO_SUBDOMAINrequiredKOMMO_ACCESS_TOKENsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"kommo-crm": {
"command": "npx",
"args": [
"-y",
"@syncraengine/kommo-mcp"
],
"env": {
"KOMMO_SUBDOMAIN": "<KOMMO_SUBDOMAIN value>",
"KOMMO_ACCESS_TOKEN": "<your KOMMO_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Keys and settings
KOMMO_SUBDOMAINrequiredKOMMO_ACCESS_TOKENsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
code --add-mcp '{"name":"kommo-crm","type":"stdio","command":"npx","args":["-y","@syncraengine/kommo-mcp"],"env":{"KOMMO_SUBDOMAIN":"<KOMMO_SUBDOMAIN value>","KOMMO_ACCESS_TOKEN":"<your KOMMO_ACCESS_TOKEN>"}}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"kommo-crm": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@syncraengine/kommo-mcp"
],
"env": {
"KOMMO_SUBDOMAIN": "<KOMMO_SUBDOMAIN value>",
"KOMMO_ACCESS_TOKEN": "<your KOMMO_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
KOMMO_SUBDOMAINrequiredKOMMO_ACCESS_TOKENsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
codex mcp add kommo-crm --env 'KOMMO_SUBDOMAIN=<KOMMO_SUBDOMAIN value>' --env 'KOMMO_ACCESS_TOKEN=<your KOMMO_ACCESS_TOKEN>' -- npx -y @syncraengine/kommo-mcpOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.kommo-crm]
command = "npx"
args = ["-y", "@syncraengine/kommo-mcp"]
env = { KOMMO_SUBDOMAIN = "<KOMMO_SUBDOMAIN value>", KOMMO_ACCESS_TOKEN = "<your KOMMO_ACCESS_TOKEN>" }If the file already exists, append the block to the end.
Keys and settings
KOMMO_SUBDOMAINrequiredKOMMO_ACCESS_TOKENsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"kommo-crm": {
"command": "npx",
"args": [
"-y",
"@syncraengine/kommo-mcp"
],
"env": {
"KOMMO_SUBDOMAIN": "<KOMMO_SUBDOMAIN value>",
"KOMMO_ACCESS_TOKEN": "<your KOMMO_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
KOMMO_SUBDOMAINrequiredKOMMO_ACCESS_TOKENsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"kommo-crm": {
"command": "npx",
"args": [
"-y",
"@syncraengine/kommo-mcp"
],
"env": {
"KOMMO_SUBDOMAIN": "<KOMMO_SUBDOMAIN value>",
"KOMMO_ACCESS_TOKEN": "<your KOMMO_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Keys and settings
KOMMO_SUBDOMAINrequiredKOMMO_ACCESS_TOKENsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"kommo-crm": {
"command": "npx",
"args": [
"-y",
"@syncraengine/kommo-mcp"
],
"env": {
"KOMMO_SUBDOMAIN": "<KOMMO_SUBDOMAIN value>",
"KOMMO_ACCESS_TOKEN": "<your KOMMO_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Keys and settings
KOMMO_SUBDOMAINrequiredKOMMO_ACCESS_TOKENsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"kommo-crm": {
"command": "npx",
"args": [
"-y",
"@syncraengine/kommo-mcp"
],
"env": {
"KOMMO_SUBDOMAIN": "<KOMMO_SUBDOMAIN value>",
"KOMMO_ACCESS_TOKEN": "<your KOMMO_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
KOMMO_SUBDOMAINrequiredKOMMO_ACCESS_TOKENsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"kommo-crm": {
"type": "local",
"command": [
"npx",
"-y",
"@syncraengine/kommo-mcp"
],
"environment": {
"KOMMO_SUBDOMAIN": "<KOMMO_SUBDOMAIN value>",
"KOMMO_ACCESS_TOKEN": "<your KOMMO_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
KOMMO_SUBDOMAINrequiredKOMMO_ACCESS_TOKENsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"kommo-crm": {
"command": "npx",
"args": [
"-y",
"@syncraengine/kommo-mcp"
],
"env": {
"KOMMO_SUBDOMAIN": "<KOMMO_SUBDOMAIN value>",
"KOMMO_ACCESS_TOKEN": "<your KOMMO_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
KOMMO_SUBDOMAINrequiredKOMMO_ACCESS_TOKENsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"kommo-crm": {
"command": "npx",
"args": [
"-y",
"@syncraengine/kommo-mcp"
],
"env": {
"KOMMO_SUBDOMAIN": "<KOMMO_SUBDOMAIN value>",
"KOMMO_ACCESS_TOKEN": "<your KOMMO_ACCESS_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
KOMMO_SUBDOMAINrequiredKOMMO_ACCESS_TOKENsecret, required
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add a kommo-crm server to claude_desktop_config.json with command npx, args ["-y", "@syncraengine/kommo-mcp"] and the KOMMO_SUBDOMAIN and KOMMO_ACCESS_TOKEN environment variables, then restart Claude Desktop.
Other ways from the author
npm install @syncraengine/kommo-mcpInstall the package for use as an SDK in your own code.
This is third-party code. Review the repository files before installing.
What it does
The @syncraengine/kommo-mcp package is published on npm and works two ways. As an MCP server it connects to Claude Desktop or another client via npx and gives about 40 tools: full management of leads, contacts, companies, tasks and notes, pipelines and stages, smart custom field search by name, catalogs and products linked to leads. As a library the same package can be imported into a TypeScript or JavaScript project and its functions, like searchContactByPhone or createLead, called directly without the MCP protocol. Tools are described as semantic and tuned for LLM convenience, and the build ships as both ESM and CommonJS.
Who it is for. For developers who want both an MCP server for an agent and a type-safe SDK for their own Kommo application from the same package.
Good fit when
- You want to connect Kommo to Claude Desktop with a one-line npx setup
- You need a typed TypeScript SDK for the Kommo API v4 in your own code, beyond MCP
- You work with Kommo catalogs and products and want to link them to leads
Not a fit when
- Your CRM is the Russian amoCRM, not the international Kommo
- You are not using Node.js and the npm ecosystem
Example request
Find a contact by phone in Kommo and create a new 500 dollar deal for themLimitations
Kommo is an international product, separate from the Russian amoCRM since 2022. Authorization is only through a long-lived access token; the README does not describe a separate OAuth flow. The package is new, with no independent code audit; trust rests on the README and the MIT license alone.
How to disable. Remove the kommo-crm entry from mcpServers in your client config.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| KOMMO_ACCESS_TOKEN required, secret | Long-lived Kommo integration access token |
| KOMMO_SUBDOMAIN required | Kommo account subdomain, e.g. mycompany for mycompany.kommo.com |
Security check
- Tools create and update leads, contacts, companies and catalogs in the CRM
- A long-lived access token in the config grants full access to the Kommo account
README in short
The README describes the package as a dual-purpose solution, lists its CRUD entity, catalog and smart field-handling capabilities, gives the npm install @syncraengine/kommo-mcp command, a Claude Desktop config with environment variables, an SDK code example searching a contact by phone and creating a lead, a categorized tool list, and build and testing steps through the MCP Inspector.
FAQ
Can it be used without MCP, just as a library?
Yes, the README shows importing functions like createLead directly from the package into your TypeScript code.
What authorization does it need?
A long-lived access token from the Kommo integration settings and the account subdomain.
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