Kommo MCP: 152 tools for Kommo CRM

Kommo MCP Server

MCP server with broad coverage of Kommo API v4: 152 tools, files, conversations, analytics, OAuth with auto-refresh, and Cursor skill

  • 0 ★ on the repository
  • Last commit
  • MIT
MCP server

Broad access

Why this level

  • 152 tools cover writing to almost all Kommo entities, including webhooks and salesbots
  • OAuth tokens with auto-refresh are saved in the .kommo_tokens.json file
All reasons and checks

runitsolutions/kommo-mcp

Install

Manual install

npm install && cp .env.example .env && npm run build

Then fill .env with your Kommo data.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • 152 tools cover writing to almost all Kommo entities, including webhooks and salesbots
  • OAuth tokens with auto-refresh are saved in the .kommo_tokens.json file

This is third-party code. Review the repository files before installing.

What it does

The server wraps almost the entire Kommo API v4: leads, contacts, companies, pipelines and stages, tasks, notes, tags, custom fields, catalogs, users and roles, events, links, and unprocessed leads, as well as automation and messaging: webhooks, salesbots, conversations and messages, calls, sources, chat templates, and widgets. It includes a separate Files API with chunked upload and entity linking, plus analytics: dashboard, sales report, and funnel analytics. The author directly compares the project with three other open Kommo servers and states that it incorporates their best practices: persistent OAuth tokens, normalization of HAL responses, HTTP deployment, and fast analytical queries, while maintaining the widest API coverage. It comes with a Cursor skill that installs with a separate command and teaches the agent to configure and use this specific server.

Who it is for. For teams that need the most complete access to Kommo API from a single server: CRM entities, files, conversations, analytics, and automation.

Good fit when

  • You need maximum coverage of Kommo API v4 in one server, including files, conversations, and analytics
  • You want OAuth with auto-refresh token, 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 need a small server with a dozen basic tools, not 152 at once
  • Your CRM is the Russian amoCRM, not the international Kommo

Example request

Generate a sales report for the quarter and show funnel analytics by stages

MCP

Transport
stdio, http
Authentication
OAuth

Environment variables

KOMMO_SUBDOMAIN required
Kommo account subdomain
KOMMO_ACCESS_TOKEN secret
Long-lived token, alternative to OAuth trio
KOMMO_CLIENT_ID
Client ID for OAuth authorization with auto-refresh
MCP_TRANSPORT
stdio by default or http for Streamable HTTP on 127.0.0.1:3000

Limitations

Kommo is an international product, separate from the Russian amoCRM since 2022. Such broad API coverage means a larger surface for configuration errors and more integration permissions than needed for a narrow task: tokens should be granted only necessary rights. The rate limit is strictly set at 7 requests per second on the client side, which may be slow for large batch operations.

How to disable. Remove the kommo server from the Cursor configuration or stop the Docker container if the server is deployed in HTTP mode.

FAQ

How does this server differ from other open Kommo servers?

The README directly compares it with Miguelgbastos/Kommo-MCP, ampulex-23/KommoMCP, and cAIborg-ai/amocrm-mcp and claims the widest API coverage while preserving their best practices.

Can it connect via HTTP, not just stdio?

Yes, setting MCP_TRANSPORT=http switches the server to Streamable HTTP on 127.0.0.1:3000 with endpoints /mcp and /health.

Discussion

No questions or reviews yet.

Kommo CRM MCP server

Kommo MCP Server

A Python MCP server with OAuth for Kommo CRM: leads, contacts, pipelines, tags, tasks, and generic GET, POST, PATCH calls to the API

MCP serverBroad access
Russian stack

An MCP with 23 tools, resources and prompts for Kommo, amoCRM's international product: deals, contacts, pipelines, Salesbot

MCP serverBroad access16Repository stars
Russian stack

A self-hosted, dependency-free Node.js MCP server with 41 tools for Kommo (amoCRM): leads, pipelines, tasks, a live conversation queue, and salesbot

MCP serverBroad access1Repository stars

MCP server for monitoring multiple Kommo accounts

Kommo MCP Server — Ventas Inteligentes

A 40-tool Kommo MCP server with two modes: local stdio for Claude Code and remote HTTP for round-the-clock tasks, built for agencies with several clients

MCP serverBroad access
Russian stack

MCP server for amoCRM and Kommo: deals, contacts, tasks and pipeline reports, stalled deals and managers overdue tasks

MCP serverBroad access

README in short

The README openly compares the project with three other community Kommo servers and lists borrowed practices, provides a table of all environment variables, npm install and npm run build commands, stdio and HTTP launch instructions, a Cursor configuration example, a separate command to install the accompanying skill via npx skills add, and links to official Kommo documentation on tokens and OAuth.

README badge

Report a problem