MCP for creating Kommo pipelines with a confirmation step
kommo-integration-mcp
An MCP server that turns a described pipeline into a JSON schema and creates it in Kommo only after confirm=true, supporting several client accounts
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- create_funnel creates a pipeline, stages and custom fields in Kommo, but only after an explicit confirm=true
- clients.json stores long-lived tokens for every client account at once
Install
- Works in
Manual install
npm install && npm run buildThen copy clients.example.json to clients.json and fill in your clients.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- create_funnel creates a pipeline, stages and custom fields in Kommo, but only after an explicit confirm=true
- clients.json stores long-lived tokens for every client account at once
This is third-party code. Review the repository files before installing.
What it does
The server closes the loop between a designed sales funnel and Kommo: an agent or person describes the funnel as JSON with a name, stages and custom fields, the validate_funnel tool checks the schema and returns errors and warnings, preview_funnel shows a readable summary of what will be created, list_pipelines and list_custom_fields check that the account does not already have the same funnel, and only then does create_funnel, with a required confirm=true parameter, create the pipeline, stages and custom fields in Kommo. The server supports several client accounts in one clients.json: every tool call names a client key, and adding a new client needs no server restart.
Who it is for. For agencies and consultants designing sales funnels for several Kommo clients who want to create them from a ready schema instead of manual setup in the interface.
Good fit when
- You regularly create similar pipelines for different client Kommo accounts
- You want schema validation and a preview before actually creating a pipeline
- You run several client accounts and do not want a separate server for each
Not a fit when
- You need full CRUD over Kommo, not just creating pipelines, stages and fields
- Your CRM is the Russian amoCRM, not the international Kommo
Example request
Validate and preview the funnel for client cliente-a, and after I confirm, create it in KommoMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
KOMMO_CLIENTS_FILE- Path to clients.json when it is not in the project root
Limitations
The toolset is narrow and deliberately limited to pipelines, stages and custom fields: no lead, contact or task operations. The clients.json file stores every client's token in one place, and the author recommends 600 permissions on it. Kommo is an international product, separate from the Russian amoCRM since 2022.
How to disable. Remove the kommo-integration server from your MCP client config.
FAQ
Can the tool create a pipeline without confirmation?
No, create_funnel requires the confirm parameter to be true, a deliberate safeguard against accidental creation.
Do I need to restart the server when adding a client?
No, the README states that editing clients.json and calling list_clients again is enough.
Discussion
No questions or reviews yet.
Related
MCP serversKommo 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
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
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
An MCP with 23 tools, resources and prompts for Kommo, amoCRM's international product: deals, contacts, pipelines, Salesbot
A self-hosted, dependency-free Node.js MCP server with 41 tools for Kommo (amoCRM): leads, pipelines, tasks, a live conversation queue, and salesbot
Multi-tenant Kommo CRM MCP server
Kommo CRM MCP Server (multi-tenant)
A centralized Kommo MCP server for an agency with several client accounts: tokens live on the VPS, the agent finds the account by client_slug
README in short
The Portuguese README describes the validate-and-create funnel cycle, gives a table of six tools noting which ones write to Kommo, shows the funnel JSON format with stages and fields, npm install and npm run build setup steps, a clients.json example with several clients, and a security section noting the file must never be committed and its permissions should be restricted.