Kommo MCP server with token auto-refresh
Kommo MCP Server
A Kommo (amoCRM) MCP server with a ready npm package and automatic access-token refresh
- 3 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Tools create and change deals, contacts, companies and tasks in a real account
- Access and refresh tokens are stored in the MCP client configuration
Install
- Works in
- Services
Manual install
npm install -g kommo-mcp-serverThe recommended method from the README.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Tools create and change deals, contacts, companies and tasks in a real account
- Access and refresh tokens are stored in the MCP client configuration
This is third-party code. Review the repository files before installing.
What it does
The server wraps the Kommo REST API v4 with roughly thirty tools: leads, contacts, companies, tasks, pipelines, users, notes, custom fields, tags, global search and webhooks. A separate create_lead_complex tool creates a lead together with a contact and a company in one request. If a refresh token, client id and client secret are configured, the server refreshes an expired access token automatically with no manual step. On a 429 response from Kommo, the server waits and retries on its own.
Who it is for. For people who want to install a Kommo MCP with one npx command and not track token expiry by hand.
Good fit when
- You want a one-command npx install with no build from source
- Your access token expires and you need automatic refresh via a refresh token
- You need to create complex deals with a contact and company in a single request
Not a fit when
- You need to send messages to customers through Kommo: the README states the server does not do this
- The README's promotional block about a separate community and a free widget is unrelated to the MCP itself and can be ignored
Example request
Create a deal for Big Company Project worth $100,000 with contact John Smith and company Big Company IncMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
KOMMO_SUBDOMAINrequired- Your Kommo account subdomain, e.g. mycompany from mycompany.kommo.com.
KOMMO_ACCESS_TOKENrequired, secret- Access token from a private integration or OAuth2.
KOMMO_REFRESH_TOKENsecret- Refresh token for automatically renewing an expired access token.
KOMMO_CLIENT_ID- The integration's client ID, needed alongside the refresh token.
KOMMO_CLIENT_SECRETsecret- The integration's client secret, needed alongside the refresh token.
Limitations
2 stars. Part of the README promotes the author's separate community in Brazil and a messaging widget, which are unrelated to what the MCP itself does. Kommo rate limits are handled by automatic wait-and-retry, but the README recommends custom batch processing for high volume.
How to disable. Remove the kommo entry from your MCP client configuration, for example claude_desktop_config.json.
FAQ
What is needed for automatic token refresh?
Set KOMMO_REFRESH_TOKEN, KOMMO_CLIENT_ID and KOMMO_CLIENT_SECRET in the config alongside the access token.
Can the server send messages to customers?
No, the README explicitly excludes this and points to the author's separate product for it.
Discussion
No questions or reviews yet.
Related
All amoCRM toolsA self-hosted, dependency-free Node.js MCP server with 41 tools for Kommo (amoCRM): leads, pipelines, tasks, a live conversation queue, and salesbot
An MCP with 23 tools, resources and prompts for Kommo, amoCRM's international product: deals, contacts, pipelines, Salesbot
MCP server for amoCRM and Kommo: deals, contacts, tasks and pipeline reports, stalled deals and managers overdue tasks
MCP server for the amoCRM (Kommo) API v4: leads, contacts, companies, tasks, pipelines, unsorted inbox and analytics
A minimal MCP server for amoCRM API v4: read and create leads, contacts and notes, with OAuth2 and long-term tokens
amoCRM MCP Server on FastMCP
amoCRM MCP Server
A FastMCP-based MCP server with 39 tools across 11 amoCRM domains: leads, contacts, analytics and batch operations, deployed as one Vercel project per account
README in short
The README lists lead, contact, company, task, pipeline, user, note, custom field, tag, search and webhook management, gives npm and source install instructions, Claude Desktop config for macOS and Windows plus Claude Code CLI, natural-language usage examples, and a section on rate limits and token refresh. It also has a promotional block about a separate Brazilian Kommo community unrelated to the server itself.