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.
Guided setup
Connect Kommo to Microsoft Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect Kommo in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
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 + Microsoft Copilot
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.
amoCRM accounts: Kommo is the international edition of amoCRM. An account whose address ends in .amocrm.ru (or the old .amocrm.com, which forwards there) does not work with this connector: use the amoCRM connector instead.
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.
Notes and events: kommo_list_notes reads the timeline of one lead, contact or company. kommo_list_notes_by_type reads the notes of all leads, contacts or companies at once, filtered by note type, record or last update, for example every call logged this week. kommo_list_events reads the account's event log: stage changes, new records, changes to fields and responsible users, calls, chat messages and completed tasks, each with who did it and when.
Already installed? The notes-by-type and event log tools reach a connector you installed earlier through its catalog update: open the connector in AnythingMCP and, under Catalog update available, check the list of new tools and click Apply update. Your token and any tools you added yourself stay as they are.
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 Microsoft Copilot
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.
Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
- Try it in the agent's Test pane: ask for something that needs the
Kommotools. - Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.
Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.
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_list_notes_by_type | Read notes across all leads, contacts or companies at once, not just one record: id, entity_id of the record it belongs to, type (common… |
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 |
kommo_list_events | Read the account's event log: who did what and when |
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."
- "Which leads moved to Closed-won or Closed-lost this week, and who moved them?"
- "List every call logged on leads since Monday, with the lead it belongs to."
FAQ
Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.
What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.
The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.
Next steps
- Connector landing page
- Connect to Claude
- Connect to ChatGPT
- Connect to Cursor
- Connect to Gemini
- Connect to Meta Muse
Was this guide helpful?
