Kommo (BYOK) — connector documentation
- MCP endpoint:
https://byok-kommo.connectorbay.com/mcp - REST API:
POST https://byok-kommo.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-kommo.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Kommo Kommo long-lived token, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-kommo.connectorbay.com/health· Tool schemas:https://byok-kommo.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-kommo · agent@connectorbay.com
What Kommo (BYOK) is for
Kommo (BYOK) lets an AI assistant read your own Kommo data through the Kommo API with a key you supply (Kommo long-lived token). Read-only: 8 tools (get_account, list_leads, list_pipelines, list_loss_reasons, list_tasks, list_tags, list_sources, list_salesbots). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to *.kommo.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Kommo. Kommo and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Which Kommo account is this token connected to?"
- "Which Kommo leads were created this week?"
- "What stages does our Kommo sales pipeline have?"
- "Which loss reasons are set up in Kommo?"
- "Which Kommo tasks are still open?"
- "Which tags do we use on Kommo leads?"
What it does
get_account: Show the Kommo account: id, name, subdomain, country, currency, whether unsorted leads and loss reasons are enabled, and the API version.list_leads: List leads with name, price, pipeline and stage ids, responsible user, loss reason, timestamps, custom field values, tags and linked companies.list_pipelines: List the lead pipelines with name, order, main/archive flags and their stages (id, name, color, type).list_loss_reasons: List the reasons a lead can be marked lost, with id, name and dates.list_tasks: List tasks with text, type, linked entity, responsible user, completion state and due time (Unix seconds).list_tags: List the tags used on leads, contacts or companies with id and name.list_sources: List the integration sources for incoming leads with name, external id, pipeline and origin code.list_salesbots: List the Salesbots with id, name, functionality type (for example regular or greeting) and whether they are active.
BYOK key
You bring your own Kommo Kommo long-lived token (https://developers.kommo.com/docs/long-lived-token). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to *.kommo.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Notices
Create a private integration in Kommo and generate a long-lived token under Keys and scopes. Kommo's chat API is a separate paid package and is not used here. Timestamps are Unix seconds.
Data sources
- https://developers.kommo.com/reference/kommo-api-reference (the API this connector calls, with a BYOK key)
Live from the Kommo API (*.kommo.com) with a BYOK key; documentation: https://developers.kommo.com/reference/kommo-api-reference. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Kommo. Kommo and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Kommo account.
Built for: Worldwide. Languages: English.