Kommo CRM MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KOMMO_BASE_URL | No | Full URL (e.g., 'https://mycompany.kommo.com') | |
| KOMMO_SUBDOMAIN | No | Your Kommo subdomain (e.g., 'mycompany' for 'mycompany.kommo.com') | |
| KOMMO_ACCESS_TOKEN | No | OAuth 2.0 Access Token (Long-lived recommended for MCP) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kommo_search_contact_by_phoneC | Search for contacts by phone number |
| kommo_search_contact_by_emailC | Search for contacts by email |
| kommo_get_contactB | Get a contact by ID |
| kommo_create_contactC | Create a new contact |
| kommo_list_leadsC | List leads with filters |
| kommo_get_leadC | Get a lead by ID |
| kommo_create_leadC | Create a new lead |
| kommo_update_leadC | Update an existing lead |
| kommo_search_leadC | Search for leads by query |
| kommo_list_pipelinesB | List all pipelines |
| kommo_create_taskC | Create a new task |
| kommo_update_lead_custom_fieldsC | Update lead custom fields by name |
| kommo_search_companyC | Search for companies by query |
| kommo_get_companyC | Get a company by ID |
| kommo_list_companiesC | List all companies |
| kommo_create_companyC | Create a new company |
| kommo_list_dealsC | List deals with filters |
| kommo_create_dealD | Create a new deal |
| kommo_list_catalogsA | List all catalogs (e.g., Products, Services) |
| kommo_list_catalog_elementsC | List elements (products) within a catalog |
| kommo_link_product_to_leadC | Link a product/catalog element to a lead |
| kommo_list_notesC | List notes for a specific entity |
| kommo_create_noteC | Create a new note for an entity |
| kommo_get_pipeline_statusesA | Get all statuses (stages) for a specific pipeline. IMPORTANT: Use this to find a valid status_id before moving a lead to a different pipeline. |
| kommo_link_lead_to_contactC | Link a lead to a contact |
| kommo_get_leads_by_contactB | Get all leads associated with a contact |
| kommo_unlink_product_from_leadC | Unlink a product/catalog element from a lead |
| kommo_get_select_field_optionsB | Get valid options for a select/dropdown custom field |
| kommo_list_contactsC | List contacts with filters |
| kommo_update_contactC | Update an existing contact |
| kommo_update_companyC | Update an existing company |
| kommo_search_dealC | Search for deals by query |
| kommo_get_dealB | Get a deal by ID |
| kommo_update_dealD | Update an existing deal |
| kommo_list_tasksC | List tasks with filters |
| kommo_get_taskB | Get a task by ID |
| kommo_update_taskC | Update an existing task |
| kommo_get_noteC | Get a specific note |
| kommo_update_noteC | Update an existing note |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 39 tools
Most tools target distinct entities and actions. There is minor overlap between 'list' and 'search' tools for the same entity (e.g., kommo_list_leads vs kommo_search_lead), but descriptions clarify their different use cases.
All tools follow the consistent pattern 'kommo_[verb]_[entity]' using snake_case. Minor deviations like 'search_contact_by_email' are predictable and do not harm coherence.
With 39 tools, the set is on the higher end but still scoped appropriately for a comprehensive CRM. Each major entity has several operations, and the count feels justified.
The tool set lacks delete operations for all entities (company, contact, deal, lead, note, task) and is missing create/update operations for pipelines and catalog elements. These are significant gaps for full lifecycle management.