Kommo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KOMMO_SUBDOMAIN | Yes | Your Kommo subdomain (e.g., 'agenciadodavid' from 'agenciadodavid.kommo.com') | |
| KOMMO_ACCESS_TOKEN | Yes | Your long-lived bearer token from Kommo private integration |
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 |
|---|---|
| search_leadsA | Robust search for leads in Kommo. Supports exact query, or smart search by phone, CPF, email, or name. Always returns associated contacts using ?with=contacts. |
| get_leadA | Get details for a specific lead by ID. |
| search_contactsA | Robust search for contacts in Kommo. Supports exact query, or smart search by phone, CPF, email, or name (automatically tries multiple variations like removing/adding 9th digit, international formats). Always returns associated leads using ?with=leads. |
| get_contactB | Get details for a specific contact by ID. |
| list_usersA | List all users in the Kommo account. Useful for finding the responsible_user_id. |
| create_taskB | Create a new task (call, meeting, email) for a specific entity (lead, contact). |
| add_lead_noteB | Add a text note to a lead (useful for AI summaries or logs). |
| list_custom_fieldsA | List custom fields and their Enums/IDs for Leads or Contacts. Highly recommended before creating or updating complex leads. |
| create_custom_fieldA | Create a new custom field for leads, contacts, or companies. Supported types: text, numeric, checkbox, select, multiselect, date, url, textarea, etc. |
| update_custom_fieldA | Update an existing custom field (e.g. rename it, or add new enums). |
| link_entitiesB | Link two entities together (e.g. link a contact to a lead, or a company to a lead). |
| get_companiesB | List companies in the CRM. |
| create_companyB | Create a new company in the CRM. |
| create_webhookB | Create a new webhook to receive real-time events from Kommo. |
| run_salesbotB | Trigger a specific salesbot for a lead or contact. |
| update_leadA | Update an existing Lead in Kommo. Automatically maps custom field NAMES to their IDs, formats timestamps for dates. Does NOT update contacts. |
| update_contactA | Update an existing Contact in Kommo. Automatically maps custom field NAMES to their IDs, formats timestamps for dates, and handles Smart Address structures. Does NOT update leads. |
| create_lead_complexA | Creates a new lead and links it to a new contact in Kommo in a single request. BUT BEFORE CREATING: it will automatically attempt to search for the contact using the provided 'phone', 'cpf', 'email' or 'contact_name'. If a contact already exists, it will UPDATE the contact and its lead instead. Automatically maps custom field NAMES to their IDs. |
| manage_lead_tagsA | Add or remove tags from a Kommo lead. Expects arrays 'tags_to_add' and/or 'tags_to_delete' containing objects with a 'name' property, matching the n8n node format. |
| get_pipelinesA | List all pipelines (funnels) and their respective statuses (stages). Use this to understand the commercial structure. |
| get_pipeline_statusesA | List all stages (statuses) of a specific pipeline (funnel), including their descriptions (tips). Use this to see what each stage means. |
| create_pipelineB | Create a new pipeline (sales funnel) in Kommo. |
| add_pipeline_stageC | Add a new stage (status) to an existing pipeline in Kommo. |
| rename_pipelineB | Rename an existing pipeline (funnel) in Kommo. |
| rename_pipeline_stageB | Rename an existing stage/status inside a pipeline, or change its color, sorting, and descriptions (tips). |
| kommo_api_requestA | Make a raw custom HTTP request to the Kommo v4 API. VERY POWERFUL: Use this to interact with any Kommo API endpoint (custom fields, notes, tasks, advanced lead filtering) after reading the Kommo official documentation. |
| send_whatsapp_messageA | Send a WhatsApp message to a specific Kommo Lead. Handles both open and closed chat sessions automatically uses the Amojo internal API. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wdavidce/kommo-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server