Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Kommo in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Let your AI work in Kommo CRM: find and update leads across pipelines, look up contacts and companies, follow tasks and notes, and log new tasks and notes. One account, with a long-lived token from a private integration.
Try asking
Example prompts for Kommo
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Kommo, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Kommo + Gemini
Let your AI work in Kommo CRM: find and update leads across pipelines, look up contacts and companies, follow tasks and notes, and log new tasks and notes. One account, with a long-lived token from a private integration.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
KOMMO_SUBDOMAIN, KOMMO_ACCESS_TOKEN
Step 1 — Get credentials
- In Kommo, open Settings → Integrations and click Create integration (top right). You need to be an account administrator.
- Choose a private integration, leave Redirect URL empty, keep the access scopes you need and click Save.
- Open the integration's Keys and scopes tab and click Generate long-lived token. Pick an expiry date and copy the token right away: Kommo shows it only once.
- Paste the token into
KOMMO_ACCESS_TOKENand your account's subdomain intoKOMMO_SUBDOMAIN: forhttps://acme.kommo.com, enteracme. Then install the connector. - Start with
kommo_get_account: it shows the account, its currency and its task types.
Whose token: the token acts as the administrator who created it. Revoke it on the integration's Authorization tab. When it expires, generate a new one and paste it in.
Read-only setup: Kommo tokens cannot be limited to reading, so disable kommo_create_lead, kommo_update_lead, kommo_create_contact, kommo_create_task and kommo_add_note. Nothing in this connector deletes data.
Pipelines, stages and fields: every lead sits in a stage of a pipeline, and kommo_list_pipelines lists them. In every pipeline, stage 142 is Closed-won and 143 is Closed-lost. Phone numbers, email addresses and any other extra data are custom fields, listed with their ids and options by kommo_list_custom_fields.
Limits: Kommo allows at most 7 requests per second per account. Over it, Kommo answers 429, and repeated violations block the IP address with 403 for every call. Ask the AI to filter or search instead of paging through all leads.
Common errors: 401 means the token is wrong, expired or revoked: generate a new one. 402 means the account's subscription has lapsed. 403 can mean that the token's user lacks rights or that the IP address was blocked after too many requests. 404 means a wrong id or subdomain. 400 lists the invalid fields, for example a stage that does not belong to the pipeline or a custom field value of the wrong type.
The connector does not delete anything and does not handle incoming (unsorted) leads, chats and messages, lists (catalogs), webhooks or Salesbot.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Gemini
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Gemini CLI reads MCP servers from ~/.gemini/settings.json (on Windows %USERPROFILE%\.gemini\settings.json). Add:
{
"mcpServers": {
"anythingmcp": {
"httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
"headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
}
}
}
- Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of
YOUR_MCP_API_KEY. - Save the file and restart
gemini. - Run
/mcpinside Gemini CLI (orgemini mcp listin your shell):anythingmcpshould show as connected. - Start prompting: Gemini CLI can now call the
Kommotools.
Available tools
| Tool | What it does |
|---|---|
kommo_get_account | Get the Kommo account: id, name, subdomain, current user id, country, currency, language, and with the default extras its task types (ids… |
kommo_list_leads | List or search leads (deals): id, name, price, pipeline and stage (status_id), responsible user, dates, tags, custom fields and, with… |
kommo_get_lead | Get one lead by id with its name, price, pipeline, stage, responsible user, dates, tags, custom field values, linked company and, by… |
kommo_create_lead | Create a lead, optionally in a given pipeline and stage, with price, responsible user, custom fields, tags and links to existing contacts… |
kommo_update_lead | Change a lead: name, price, stage or pipeline (moving it through the funnel; Closed-won is status 142, Closed-lost 143), responsible user… |
kommo_list_contacts | List or search contacts: id, name, first and last name, responsible user, dates, tags, custom fields (phone and email are custom fields)… |
kommo_get_contact | Get one contact by id with names, responsible user, tags, custom field values (phones, emails, position), linked companies and, by default… |
kommo_create_contact | Create a contact with name, responsible user, phone, email and other custom fields, and tags |
kommo_list_companies | List or search companies: id, name, responsible user, dates, tags, custom fields and, with with=leads,contacts, linked leads and contacts |
kommo_list_pipelines | List the lead pipelines with their stages: pipeline id, name, whether main or archived, and per stage (in _embedded.statuses) its id, name… |
kommo_list_custom_fields | List the custom fields of leads, contacts or companies: id, name, code (PHONE, EMAIL for contacts), type and, for select fields, the enum… |
kommo_list_tasks | List tasks: id, text, type, deadline (complete_till), whether completed, result, responsible user and the lead, contact or company it… |
kommo_create_task | Create a task with a deadline, linked to a lead, contact or company, for a responsible user |
kommo_list_notes | Read the notes (timeline entries) of one lead, contact or company: id, type (common text note, call_in, call_out, sms, service messages… |
kommo_add_note | Add a text note to the timeline of a lead, contact or company |
kommo_list_users | List the account's users: id, name, email, language and rights, and with with=role,group their role and group |
Example prompts
- "Which leads in the Sales pipeline have been in the Negotiation stage for more than two weeks?"
- "Find the contact Maria Lopez and show me her phone number and her open leads."
- "Move the lead 'Website redesign for Nova' to Closed-won and add a note that the contract was signed."
- "Create a call task for tomorrow at 10:00 on the lead 'Fleet order 2026' for the responsible manager."
FAQ
Where does Gemini CLI look for MCP servers? In ~/.gemini/settings.json for your user, or in .gemini/settings.json inside a project. gemini mcp list shows each server and whether it connects.
Next steps
Was this guide helpful?
