SkillFoxx

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

  • 0 ★ on the repository
  • Last commit
MCP server

Broad access

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
All reasons and checks

feniaxcrm-cloud/kommo-mcp-ventas-inteligentesAuthor:feniaxcrm-cloud

Install

Manual install

git clone https://github.com/feniaxcrm-cloud/kommo-mcp-ventas-inteligentes.git && cd kommo-mcp-ventas-inteligentes && npm install && npm run build

Then copy accounts.example.json to accounts.json and fill in your accounts.

Access and checks

How we review

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

  • 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

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 today

MCP

Transport
stdio, http
Authentication
key is optional

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

Limitations

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.

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.

Discussion

No questions or reviews yet.

MCP servers

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

MCP serverBroad access

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

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 access16

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

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 access1
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 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.

README badge

Report a problem