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
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 and templates across several Kommo accounts at once
- Long-lived tokens for every client account are stored in a single file or environment variable
Install
Manual install
git clone https://github.com/feniaxcrm-cloud/kommo-mcp-ventas-inteligentes.git && cd kommo-mcp-ventas-inteligentes && npm install && npm run buildThen copy accounts.example.json to accounts.json and fill in your accounts.
This is third-party code. Review the repository files before installing.
What it does
The server gives an agent 40 tools for Kommo CRM, grouped by leads, contacts, companies, pipelines, tasks, events, conversations, salesbots, message templates and settings like tags and loss reasons, plus a combined dashboard across all accounts at once. Its key feature: the server reads the account list from accounts.json and can poll one to a hundred Kommo accounts from a single place, useful for agencies and consultants running several clients. Local mode runs over stdio for Claude Code and Claude Desktop, and remote mode brings up a Streamable HTTP server for clients like Cowork and for tasks that need to run without the user's computer being on.
Who it is for. For agencies, partners and consultants running several client accounts in Kommo who want a combined summary across all of them.
Good fit when
- You run several Kommo accounts and want one combined dashboard instead of switching between them
- You need both local Claude Code work and a remote HTTP mode for background tasks
- You need tools for salesbots and conversations, not just basic CRM entities
Not a fit when
- You have a single Kommo account, so multi-account support is unnecessary
- You want a ready cloud deploy without Docker or Railway
Example request
Give me a summary across all client Kommo accounts: how many new leads and unread chats todayLimitations
All account tokens live in one accounts.json file locally, or one KOMMO_ACCOUNTS environment variable remotely; compromising the server risks every connected client at once. Remote mode has to be self-hosted on Railway, a VPS or Docker; there is no ready cloud address from the author. Kommo's long-lived tokens are valid for up to five years and have to be revoked manually through the Kommo interface when needed.
How to disable. Remove the kommo server from your local client's .mcp.json, or stop the deploy on Railway or your own server.
MCP
- Transport
- stdio, http
- Authentication
- API key
| Environment variables | |
|---|---|
| KOMMO_ACCOUNTS secret | A JSON array of accounts with name, subdomain and token, used in remote mode instead of accounts.json |
| PORT | Remote HTTP server port, defaults to 3000 |
Security check
- Tools create and update leads, contacts and templates across several Kommo accounts at once
- Long-lived tokens for every client account are stored in a single file or environment variable
README in short
The Spanish README describes the two operating modes in a table, lists the 40 tools by category, gives local install steps with npm install, npm run build and filling in accounts.json, separate steps for a remote Railway deploy with the KOMMO_ACCOUNTS variable and a Docker alternative, explains getting a long-lived token in Kommo, and a security section about keeping accounts.json out of git.
FAQ
Do I need to restart the server when adding a new account?
In local mode yes, the client needs a restart after editing accounts.json; in remote mode it depends on the deploy method.
What is the difference between local and remote mode?
Local mode runs over stdio with npm start for Claude Code and Desktop, remote mode brings up an HTTP server with npm run start:remote for clients like Cowork and background tasks.
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