# Kommo CRM (pypi · kommo-kiro-power)

Manage Kommo CRM leads, contacts, pipelines, tasks, notes, tags and companies.

- Trust score: 65/100 (medium)
- Change this week: −15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `kommo-kiro-power`: 65/100 (this document), [markdown](https://verifymcp.io/servers/depper-ia-kommo-kiro-power/kommo-kiro-power.md), [page](https://verifymcp.io/servers/depper-ia-kommo-kiro-power/kommo-kiro-power)

## Channel facts

- Registry: `pypi`
- Package: `kommo-kiro-power`
- Version: `1.0.5`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 0 of 28 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 48 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3755 tokens (~125/item across 30 items; 30 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Kommo CRM MCP server?

Kommo CRM runs locally as a PyPI package, launched with uvx kommo-kiro-power. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add depper-ia-kommo-kiro-power -- uvx kommo-kiro-power
```

### Cursor

```json
{
  "mcpServers": {
    "depper-ia-kommo-kiro-power": {
      "command": "uvx",
      "args": [
        "kommo-kiro-power"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "depper-ia-kommo-kiro-power": {
      "command": "uvx",
      "args": [
        "kommo-kiro-power"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add depper-ia-kommo-kiro-power -- uvx kommo-kiro-power
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "depper-ia-kommo-kiro-power": {
      "type": "local",
      "command": [
        "uvx",
        "kommo-kiro-power"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add depper-ia-kommo-kiro-power --command uvx --arg kommo-kiro-power
```

### Hermes

```yaml
mcp_servers:
  depper-ia-kommo-kiro-power:
    command: "uvx"
    args: ["kommo-kiro-power"]
```

### Netclaw

```json
{
  "McpServers": {
    "depper-ia-kommo-kiro-power": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "kommo-kiro-power"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add depper-ia-kommo-kiro-power -t stdio -c uvx -a kommo-kiro-power
```

### Other

```json
{
  "mcpServers": {
    "depper-ia-kommo-kiro-power": {
      "command": "uvx",
      "args": [
        "kommo-kiro-power"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 65, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-19 (score 80, +16)

- [security improvement] Malware scan: unverified → pass
- [security] Stability: 0.97 → pass

### 2026-11-18 (score 64, −1)

- [functional] Stability: pass → 0.97

### 2026-11-15 (score 65, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-13 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-12 (score 65, +1)

- [security] Stability: 0.97 → pass

### 2026-11-10 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 63, −15)

- [security regression] Malware scan: pass → unverified

## MCP tools (30)

### `list_leads` (~131 tokens)

List leads, optionally filtered by pipeline and stage. Read-only. Returns an array of lead objects with embedded contacts and tags, up to `limit` items (follows Kommo pagination when limit exceeds 50). To fetch custom fields for one lead, use get_lead.

Input parameters:

- `limit` (integer): Maximum number of leads to return. Default 50.
- `pipeline_id` (integer): Only leads in this pipeline. Get IDs from list_pipelines.
- `stage_id` (integer): Only leads in this stage. Ignored unless pipeline_id is also set. Get IDs from list_stages.

Output parameters:

- `items` (array): Returned entities.

### `get_lead` (~74 tokens)

Fetch one lead by ID. Read-only. Returns the full lead object including embedded contacts, tags, and custom_fields_values. Use list_leads instead to browse or find lead IDs.

Input parameters:

- `lead_id` (integer, required): Kommo lead ID (integer). Obtain it from list_leads or from the create_lead result.

Output parameters:

- `_embedded` (object): Embedded tags, contacts and companies.
- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `account_id` (integer|null): Kommo account ID.
- `closed_at` (integer|null): Closing time, Unix seconds, or null.
- `closest_task_at` (integer|null): Next task deadline, Unix seconds, or null.
- `created_at` (integer|null): Creation time, Unix seconds.
- `created_by` (integer|null): ID of the user who created it.
- `custom_fields_values` (array|null): Custom field values in Kommo format: objects with field_id, field_code and values.
- `group_id` (integer|null): ID of the responsible user's group.
- `id` (integer): Lead ID.
- `is_deleted` (boolean|null): Whether the lead is deleted.
- `loss_reason_id` (integer|null): Loss reason ID, or null.
- `name` (string|null): Lead name.
- `pipeline_id` (integer|null): Pipeline ID.
- `price` (integer|null): Lead budget.
- `responsible_user_id` (integer|null): ID of the responsible Kommo user.
- `status_id` (integer|null): Current stage ID.
- `updated_at` (integer|null): Last update time, Unix seconds.
- `updated_by` (integer|null): ID of the user who last updated it.

### `create_lead` (~294 tokens)

Create one lead in Kommo. Not idempotent: each call creates a new lead. Tag names that do not exist yet are created automatically. Returns the created lead object. To create the contact and company in the same call, use create_lead_complex.

Input parameters:

- `custom_fields_values` (array): Lead custom field values in Kommo API v4 format: a list of objects, each addressing a field by `field_id` (from list_custom_fields) or by system `field_code`, plus `values`: [{value}] (select-type fi…
- `name` (string, required): Lead name (title of the deal).
- `pipeline_id` (integer): Pipeline to create the lead in. Get IDs from list_pipelines. Omit to use the account default.
- `price` (number): Deal value in the account currency, e.g. 1500.
- `responsible_user_id` (integer): Kommo user ID to assign as owner. Omit for the default user.
- `stage_id` (integer): Stage (status) to place the lead in. Get IDs from list_stages. Omit for the first stage of the pipeline.
- `tags` (array): Tag names to attach, e.g. ["vip", "web"]. Created if missing.

Output parameters:

- `_embedded` (object): Embedded tags, contacts and companies.
- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `account_id` (integer|null): Kommo account ID.
- `closed_at` (integer|null): Closing time, Unix seconds, or null.
- `closest_task_at` (integer|null): Next task deadline, Unix seconds, or null.
- `created_at` (integer|null): Creation time, Unix seconds.
- `created_by` (integer|null): ID of the user who created it.
- `custom_fields_values` (array|null): Custom field values in Kommo format: objects with field_id, field_code and values.
- `group_id` (integer|null): ID of the responsible user's group.
- `id` (integer): Lead ID.
- `is_deleted` (boolean|null): Whether the lead is deleted.
- `loss_reason_id` (integer|null): Loss reason ID, or null.
- `name` (string|null): Lead name.
- `pipeline_id` (integer|null): Pipeline ID.
- `price` (integer|null): Lead budget.
- `responsible_user_id` (integer|null): ID of the responsible Kommo user.
- `status_id` (integer|null): Current stage ID.
- `updated_at` (integer|null): Last update time, Unix seconds.
- `updated_by` (integer|null): ID of the user who last updated it.

### `update_lead` (~189 tokens)

Update fields on an existing lead by sending `fields` as the body of a Kommo API v4 PATCH /leads/{id}. Returns the updated lead. Overwrites the given values; omitted fields are untouched. For a stage change prefer move_lead_stage; for several leads use bulk_update_leads.

Input parameters:

- `fields` (object, required): Raw Kommo v4 lead fields to change, passed through unchanged. Common keys: name (string), price (integer), status_id (stage ID), pipeline_id, responsible_user_id, custom_fields_values (array of {fiel…
- `lead_id` (integer, required): Kommo lead ID (integer). Obtain it from list_leads or from the create_lead result.

Output parameters:

- `_embedded` (object): Embedded tags, contacts and companies.
- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `account_id` (integer|null): Kommo account ID.
- `closed_at` (integer|null): Closing time, Unix seconds, or null.
- `closest_task_at` (integer|null): Next task deadline, Unix seconds, or null.
- `created_at` (integer|null): Creation time, Unix seconds.
- `created_by` (integer|null): ID of the user who created it.
- `custom_fields_values` (array|null): Custom field values in Kommo format: objects with field_id, field_code and values.
- `group_id` (integer|null): ID of the responsible user's group.
- `id` (integer): Lead ID.
- `is_deleted` (boolean|null): Whether the lead is deleted.
- `loss_reason_id` (integer|null): Loss reason ID, or null.
- `name` (string|null): Lead name.
- `pipeline_id` (integer|null): Pipeline ID.
- `price` (integer|null): Lead budget.
- `responsible_user_id` (integer|null): ID of the responsible Kommo user.
- `status_id` (integer|null): Current stage ID.
- `updated_at` (integer|null): Last update time, Unix seconds.
- `updated_by` (integer|null): ID of the user who last updated it.

### `delete_lead` (~90 tokens)

Delete a lead. Sends PATCH /leads/{id} with is_deleted=true, so the lead is soft-deleted rather than removed through a hard-delete call. Destructive: the lead disappears from normal lists. Confirm the lead_id with get_lead first.

Input parameters:

- `lead_id` (integer, required): Kommo lead ID (integer). Obtain it from list_leads or from the create_lead result.

Output parameters:

- `_embedded` (object): Embedded tags, contacts and companies.
- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `account_id` (integer|null): Kommo account ID.
- `closed_at` (integer|null): Closing time, Unix seconds, or null.
- `closest_task_at` (integer|null): Next task deadline, Unix seconds, or null.
- `created_at` (integer|null): Creation time, Unix seconds.
- `created_by` (integer|null): ID of the user who created it.
- `custom_fields_values` (array|null): Custom field values in Kommo format: objects with field_id, field_code and values.
- `group_id` (integer|null): ID of the responsible user's group.
- `id` (integer): Lead ID.
- `is_deleted` (boolean|null): Whether the lead is deleted.
- `loss_reason_id` (integer|null): Loss reason ID, or null.
- `name` (string|null): Lead name.
- `pipeline_id` (integer|null): Pipeline ID.
- `price` (integer|null): Lead budget.
- `responsible_user_id` (integer|null): ID of the responsible Kommo user.
- `status_id` (integer|null): Current stage ID.
- `updated_at` (integer|null): Last update time, Unix seconds.
- `updated_by` (integer|null): ID of the user who last updated it.

### `move_lead_stage` (~130 tokens)

Move a lead to another stage by setting its status_id (and optionally pipeline_id). Returns the updated lead. Use this instead of update_lead for pipeline moves. Pass pipeline_id when moving to a stage in a different pipeline.

Input parameters:

- `lead_id` (integer, required): Kommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
- `pipeline_id` (integer): Target pipeline ID. Only needed when the stage belongs to a different pipeline than the lead's current one.
- `stage_id` (integer, required): Target stage ID. Get IDs from list_stages.

Output parameters:

- `_embedded` (object): Embedded tags, contacts and companies.
- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `account_id` (integer|null): Kommo account ID.
- `closed_at` (integer|null): Closing time, Unix seconds, or null.
- `closest_task_at` (integer|null): Next task deadline, Unix seconds, or null.
- `created_at` (integer|null): Creation time, Unix seconds.
- `created_by` (integer|null): ID of the user who created it.
- `custom_fields_values` (array|null): Custom field values in Kommo format: objects with field_id, field_code and values.
- `group_id` (integer|null): ID of the responsible user's group.
- `id` (integer): Lead ID.
- `is_deleted` (boolean|null): Whether the lead is deleted.
- `loss_reason_id` (integer|null): Loss reason ID, or null.
- `name` (string|null): Lead name.
- `pipeline_id` (integer|null): Pipeline ID.
- `price` (integer|null): Lead budget.
- `responsible_user_id` (integer|null): ID of the responsible Kommo user.
- `status_id` (integer|null): Current stage ID.
- `updated_at` (integer|null): Last update time, Unix seconds.
- `updated_by` (integer|null): ID of the user who last updated it.

### `bulk_update_leads` (~98 tokens)

Update many leads in a single PATCH /leads request. Each item merges its `fields` with the lead `id` and uses the same field keys as update_lead. Returns the Kommo response for the batch. Use update_lead for a single lead.

Input parameters:

- `leads_updates` (array, required): Updates to apply, one per lead. Example: [{"id": 123, "fields": {"status_id": 456}}].

Output parameters:

- `_embedded` (object): Updated leads.
- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `_total_items` (integer): Number of leads updated.

### `create_lead_complex` (~318 tokens)

Create a lead together with a new contact and/or company in one request (POST /leads/complex). Not idempotent; Kommo may merge a duplicate (merged=true). Returns {id, contact_id, company_id, merged}. Contact phone and email are sent as Kommo's built-in PHONE and EMAIL fields. Use create_lead if no contact or company is needed.

Input parameters:

- `company_name` (string): Name of a new company to create and attach.
- `contact_email` (string): Contact email address.
- `contact_name` (string): Name of a new contact to create. Phone and email are ignored unless this is set.
- `contact_phone` (string): Contact phone number, e.g. +15551234567.
- `custom_fields_values` (array): Lead custom field values in Kommo API v4 format: a list of objects, each addressing a field by `field_id` (from list_custom_fields) or by system `field_code`, plus `values`: [{value}] (select-type fi…
- `name` (string, required): Lead name (title of the deal).
- `pipeline_id` (integer): Pipeline for the lead. Get IDs from list_pipelines.
- `stage_id` (integer): Stage for the lead. Get IDs from list_stages.
- `tags` (array): Tag names to attach to the lead. Created if missing.

Output parameters:

- `company_id` (integer|null): ID of the created or linked company.
- `contact_id` (integer|null): ID of the created or linked contact.
- `id` (integer): Lead ID.
- `merged` (boolean): True when Kommo merged the lead into an existing duplicate.
- `request_id` (array): Request IDs sent for this lead.

### `add_tag` (~114 tokens)

Attach a tag to a lead by name. Creates the tag if it does not exist. Reads the lead's current tags and writes back the full list plus the new one, so existing tags are kept. Safe to repeat. Returns the updated lead. See list_tags for existing tag names.

Input parameters:

- `lead_id` (integer, required): Kommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
- `tag_name` (string, required): Exact tag name (case-sensitive), e.g. "vip".

Output parameters:

- `_embedded` (object): Embedded tags, contacts and companies.
- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `account_id` (integer|null): Kommo account ID.
- `closed_at` (integer|null): Closing time, Unix seconds, or null.
- `closest_task_at` (integer|null): Next task deadline, Unix seconds, or null.
- `created_at` (integer|null): Creation time, Unix seconds.
- `created_by` (integer|null): ID of the user who created it.
- `custom_fields_values` (array|null): Custom field values in Kommo format: objects with field_id, field_code and values.
- `group_id` (integer|null): ID of the responsible user's group.
- `id` (integer): Lead ID.
- `is_deleted` (boolean|null): Whether the lead is deleted.
- `loss_reason_id` (integer|null): Loss reason ID, or null.
- `name` (string|null): Lead name.
- `pipeline_id` (integer|null): Pipeline ID.
- `price` (integer|null): Lead budget.
- `responsible_user_id` (integer|null): ID of the responsible Kommo user.
- `status_id` (integer|null): Current stage ID.
- `updated_at` (integer|null): Last update time, Unix seconds.
- `updated_by` (integer|null): ID of the user who last updated it.

### `remove_tag` (~125 tokens)

Detach a tag from a lead by name. Reads the lead's tags and writes back the list without that tag; other tags are kept. The tag itself is not deleted from the account. If no tag with that name exists, nothing changes and the lead is returned as is. Safe to repeat. Returns the updated lead.

Input parameters:

- `lead_id` (integer, required): Kommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
- `tag_name` (string, required): Exact tag name (case-sensitive) to detach, e.g. "vip".

Output parameters:

- `_embedded` (object): Embedded tags, contacts and companies.
- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `account_id` (integer|null): Kommo account ID.
- `closed_at` (integer|null): Closing time, Unix seconds, or null.
- `closest_task_at` (integer|null): Next task deadline, Unix seconds, or null.
- `created_at` (integer|null): Creation time, Unix seconds.
- `created_by` (integer|null): ID of the user who created it.
- `custom_fields_values` (array|null): Custom field values in Kommo format: objects with field_id, field_code and values.
- `group_id` (integer|null): ID of the responsible user's group.
- `id` (integer): Lead ID.
- `is_deleted` (boolean|null): Whether the lead is deleted.
- `loss_reason_id` (integer|null): Loss reason ID, or null.
- `name` (string|null): Lead name.
- `pipeline_id` (integer|null): Pipeline ID.
- `price` (integer|null): Lead budget.
- `responsible_user_id` (integer|null): ID of the responsible Kommo user.
- `status_id` (integer|null): Current stage ID.
- `updated_at` (integer|null): Last update time, Unix seconds.
- `updated_by` (integer|null): ID of the user who last updated it.

### `list_tags` (~77 tokens)

List tags defined in the account for one entity type (up to 250). Read-only. Returns tag objects with id and name. Use it to check exact tag names before add_tag or remove_tag.

Input parameters:

- `entity_type` (string): Which tag set to list: leads, contacts or companies (singular forms accepted). Default "lead".

Output parameters:

- `items` (array): Returned entities.

### `create_task` (~144 tokens)

Create a follow-up task (type 1) attached to a lead. Not idempotent: each call creates a new task. Returns the created task. Use list_tasks to review existing tasks and add_note for non-actionable remarks.

Input parameters:

- `due_date` (integer, required): Deadline as a Unix timestamp in seconds, e.g. 1767225600.
- `lead_id` (integer, required): Kommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
- `responsible_user_id` (integer): Kommo user ID responsible for the task. Omit for the default.
- `text` (string, required): Task description shown in Kommo.

Output parameters:

- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `account_id` (integer|null): Kommo account ID.
- `complete_till` (integer|null): Deadline, Unix seconds.
- `created_at` (integer|null): Creation time, Unix seconds.
- `created_by` (integer|null): ID of the user who created it.
- `duration` (integer|null): Duration in seconds.
- `entity_id` (integer|null): ID of the entity the task is attached to.
- `entity_type` (string|null): Entity type, e.g. leads.
- `group_id` (integer|null): ID of the responsible user's group.
- `id` (integer): Task ID.
- `is_completed` (boolean|null): Whether the task is completed.
- `responsible_user_id` (integer|null): ID of the responsible Kommo user.
- `result`: Completion result (object or array), may be empty.
- `task_type_id` (integer|null): Task type ID (1 is follow-up).
- `text` (string|null): Task description.
- `updated_at` (integer|null): Last update time, Unix seconds.
- `updated_by` (integer|null): ID of the user who last updated it.

### `list_tasks` (~179 tokens)

List tasks, optionally for one lead or only overdue ones. Read-only. Returns an array (Kommo default page size unless `limit` is set, max 250); pass `page` for paginated output with a has_next flag. Overdue means deadline at or before now and not completed.

Input parameters:

- `filter_overdue` (boolean): If true, only uncompleted tasks whose deadline has passed.
- `lead_id` (integer): Only tasks attached to this lead. Omit for all tasks.
- `limit` (integer): Tasks per page, max 250. Omit for Kommo's default (50).
- `page` (integer): 1-based page number. Omit for a plain array (first page). When set, returns {items, page, limit, has_next}; request page+1 while has_next is true.

Output parameters:

- `has_next` (boolean): True when another page exists (only when paginated).
- `items` (array): Returned entities.
- `limit` (integer): Page size used (only when `page` was requested).
- `page` (integer): Page number returned (only when `page` was requested).

### `add_note` (~96 tokens)

Add a plain text (common) note to a lead's timeline. Not idempotent: repeated calls add duplicate notes. Notes are internal and are not sent to the customer; use send_chat_message for that. Returns the created note.

Input parameters:

- `lead_id` (integer, required): Kommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
- `text` (string, required): Note content (plain text).

Output parameters:

- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `account_id` (integer|null): Kommo account ID.
- `created_at` (integer|null): Creation time, Unix seconds.
- `created_by` (integer|null): ID of the user who created it.
- `entity_id` (integer|null): ID of the entity the note is attached to.
- `group_id` (integer|null): ID of the responsible user's group.
- `id` (integer): Note ID.
- `note_type` (string|null): Note type, e.g. common.
- `params` (object): Note parameters, e.g. {text}.
- `responsible_user_id` (integer|null): ID of the responsible Kommo user.
- `updated_at` (integer|null): Last update time, Unix seconds.
- `updated_by` (integer|null): ID of the user who last updated it.

### `send_chat_message` (~113 tokens)

Send an outgoing chat message to the customer in a lead's conversation. Finds a conversation (talk) whose entity is this lead and posts to it; fails with an error if the lead has none. The message is delivered externally and cannot be recalled by this server, and repeated calls send duplicates. Use add_note for internal notes.

Input parameters:

- `lead_id` (integer, required): ID of a lead that already has an active conversation. Get it from list_leads.
- `text` (string, required): Message text sent to the customer.

### `list_chat_templates` (~48 tokens)

List the account's chat message templates. Read-only. Returns template objects as provided by Kommo. This server cannot send a template; it only lists them (send_chat_message sends plain text).

Output parameters:

- `items` (array): Returned entities.

### `list_contacts` (~182 tokens)

Search or list contacts. Read-only. Returns an array of up to `limit` contacts (max 250); pass `page` for paginated output with a has_next flag. Pass `query` to match by name, phone, or email; omit it to list recent contacts. Use get_contact for one contact's full details.

Input parameters:

- `limit` (integer): Contacts per page. Default 50, capped at 250.
- `page` (integer): 1-based page number. Omit for a plain array (first page). When set, returns {items, page, limit, has_next}; request page+1 while has_next is true.
- `query` (string): Free-text search matched by Kommo against name, phone, and email, e.g. "Jane" or "+15551234567". Omit to list without filtering.

Output parameters:

- `has_next` (boolean): True when another page exists (only when paginated).
- `items` (array): Returned entities.
- `limit` (integer): Page size used (only when `page` was requested).
- `page` (integer): Page number returned (only when `page` was requested).

### `get_contact` (~69 tokens)

Fetch one contact by ID. Read-only. Returns the contact with embedded tags and custom_fields_values (phone, email, and others). Use list_contacts to find the ID.

Input parameters:

- `contact_id` (integer, required): Kommo contact ID (integer). Obtain it from list_contacts or from the create_contact result.

Output parameters:

- `_embedded` (object): Embedded tags and companies.
- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `account_id` (integer|null): Kommo account ID.
- `closest_task_at` (integer|null): Next task deadline, Unix seconds, or null.
- `created_at` (integer|null): Creation time, Unix seconds.
- `created_by` (integer|null): ID of the user who created it.
- `custom_fields_values` (array|null): Custom field values in Kommo format: objects with field_id, field_code and values.
- `first_name` (string|null): First name.
- `group_id` (integer|null): ID of the responsible user's group.
- `id` (integer): Contact ID.
- `last_name` (string|null): Last name.
- `name` (string|null): Full name.
- `responsible_user_id` (integer|null): ID of the responsible Kommo user.
- `updated_at` (integer|null): Last update time, Unix seconds.
- `updated_by` (integer|null): ID of the user who last updated it.

### `create_contact` (~116 tokens)

Create one contact. Not idempotent: it does not check for duplicates, so search with list_contacts first. Phone and email are sent as Kommo's built-in PHONE and EMAIL fields (WORK values). Returns the created contact. To create a lead and contact together, use create_lead_complex.

Input parameters:

- `email` (string): Email address, e.g. jane@example.com.
- `name` (string, required): Contact full name.
- `phone` (string): Phone number, ideally international, e.g. +15551234567.

Output parameters:

- `_embedded` (object): Embedded tags and companies.
- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `account_id` (integer|null): Kommo account ID.
- `closest_task_at` (integer|null): Next task deadline, Unix seconds, or null.
- `created_at` (integer|null): Creation time, Unix seconds.
- `created_by` (integer|null): ID of the user who created it.
- `custom_fields_values` (array|null): Custom field values in Kommo format: objects with field_id, field_code and values.
- `first_name` (string|null): First name.
- `group_id` (integer|null): ID of the responsible user's group.
- `id` (integer): Contact ID.
- `last_name` (string|null): Last name.
- `name` (string|null): Full name.
- `responsible_user_id` (integer|null): ID of the responsible Kommo user.
- `updated_at` (integer|null): Last update time, Unix seconds.
- `updated_by` (integer|null): ID of the user who last updated it.

### `update_contact` (~148 tokens)

Update fields on an existing contact by sending `fields` as the body of a Kommo API v4 PATCH /contacts/{id}. Returns the updated contact. Provided values overwrite existing ones; omitted fields are untouched.

Input parameters:

- `contact_id` (integer, required): Kommo contact ID (integer). Obtain it from list_contacts or from the create_contact result.
- `fields` (object, required): Raw Kommo v4 contact fields to change, passed through unchanged. Common keys: name, first_name, last_name, responsible_user_id, custom_fields_values (array of {field_id, values: [{value, enum_code}]}…

Output parameters:

- `_embedded` (object): Embedded tags and companies.
- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `account_id` (integer|null): Kommo account ID.
- `closest_task_at` (integer|null): Next task deadline, Unix seconds, or null.
- `created_at` (integer|null): Creation time, Unix seconds.
- `created_by` (integer|null): ID of the user who created it.
- `custom_fields_values` (array|null): Custom field values in Kommo format: objects with field_id, field_code and values.
- `first_name` (string|null): First name.
- `group_id` (integer|null): ID of the responsible user's group.
- `id` (integer): Contact ID.
- `last_name` (string|null): Last name.
- `name` (string|null): Full name.
- `responsible_user_id` (integer|null): ID of the responsible Kommo user.
- `updated_at` (integer|null): Last update time, Unix seconds.
- `updated_by` (integer|null): ID of the user who last updated it.

### `list_pipelines` (~70 tokens)

List all sales pipelines in the account. Read-only. Returns pipeline objects (id, name, sort, embedded stages as provided by Kommo). Results are cached for 10 minutes, so very recent changes may not show. Start here to obtain the pipeline_id and stage IDs used by most lead tools.

Output parameters:

- `items` (array): Returned entities.

### `create_pipeline` (~66 tokens)

Create a new sales pipeline with the given name (sort order 99). Not idempotent: each call creates another pipeline. Returns the created pipeline. Add stages afterwards with create_stage. Clears the pipelines cache.

Input parameters:

- `name` (string, required): Pipeline name, e.g. "Enterprise".

Output parameters:

- `_embedded` (object): Embedded resources.
- `account_id` (integer|null): Kommo account ID.
- `id` (integer): Pipeline ID.
- `is_archive` (boolean|null): Whether the pipeline is archived.
- `is_main` (boolean|null): Whether this is the main pipeline.
- `is_unsorted_on` (boolean|null): Whether the Incoming leads stage is enabled.
- `name` (string|null): Pipeline name.
- `sort` (integer|null): Sort order.

### `update_pipeline` (~76 tokens)

Rename an existing pipeline. Only the name can be changed with this tool. Returns the updated pipeline. Safe to repeat. Clears the pipelines cache. To change a stage use update_stage.

Input parameters:

- `name` (string, required): New pipeline name.
- `pipeline_id` (integer, required): Kommo pipeline ID (integer). Obtain it from list_pipelines.

Output parameters:

- `_embedded` (object): Embedded resources.
- `account_id` (integer|null): Kommo account ID.
- `id` (integer): Pipeline ID.
- `is_archive` (boolean|null): Whether the pipeline is archived.
- `is_main` (boolean|null): Whether this is the main pipeline.
- `is_unsorted_on` (boolean|null): Whether the Incoming leads stage is enabled.
- `name` (string|null): Pipeline name.
- `sort` (integer|null): Sort order.

### `list_stages` (~87 tokens)

List the stages (statuses) of one pipeline. Read-only. Returns stage objects with id, name, sort, color, and is_editable. Results are cached for 10 minutes. Use the stage IDs with list_leads, create_lead, and move_lead_stage.

Input parameters:

- `pipeline_id` (integer, required): Kommo pipeline ID (integer). Obtain it from list_pipelines.

Output parameters:

- `items` (array): Returned entities.

### `create_stage` (~126 tokens)

Add a stage to a pipeline. It is placed after the pipeline's existing editable stages (sort is computed automatically). Not idempotent: each call creates another stage. Returns the created stage. Clears the stage and pipeline caches.

Input parameters:

- `color` (string): Hex color sent to Kommo as-is, e.g. #4CAF50. Optional; Kommo may restrict it to its own palette.
- `name` (string, required): Stage name, e.g. "Negotiation".
- `pipeline_id` (integer, required): Kommo pipeline ID (integer). Obtain it from list_pipelines.

Output parameters:

- `account_id` (integer|null): Kommo account ID.
- `color` (string|null): Hex color.
- `id` (integer): Stage ID.
- `is_editable` (boolean|null): Whether the stage can be edited.
- `name` (string|null): Stage name.
- `pipeline_id` (integer|null): Parent pipeline ID.
- `sort` (integer|null): Sort order.
- `type` (integer|null): 0 for regular stages, 1 for unsorted.

### `update_stage` (~162 tokens)

Change a stage's name, sort order, or color. Only the provided fields are sent; supply at least one of name, sort, or color. Returns the updated stage. Safe to repeat. Clears the stage and pipeline caches. Get IDs from list_stages.

Input parameters:

- `color` (string): New hex color, e.g. #4CAF50, sent to Kommo as-is.
- `name` (string): New stage name.
- `pipeline_id` (integer, required): Kommo pipeline ID (integer). Obtain it from list_pipelines.
- `sort` (integer): New sort position; lower values appear first (e.g. 10, 20).
- `stage_id` (integer, required): Stage ID within that pipeline. Obtain it from list_stages.

Output parameters:

- `account_id` (integer|null): Kommo account ID.
- `color` (string|null): Hex color.
- `id` (integer): Stage ID.
- `is_editable` (boolean|null): Whether the stage can be edited.
- `name` (string|null): Stage name.
- `pipeline_id` (integer|null): Parent pipeline ID.
- `sort` (integer|null): Sort order.
- `type` (integer|null): 0 for regular stages, 1 for unsorted.

### `list_custom_fields` (~88 tokens)

List custom field definitions for leads, contacts, or companies. Read-only. Returns field objects with id, name, code, type, and enum options. Cached for 1 hour. Use the field IDs in custom_fields_values when calling update_lead or update_contact.

Input parameters:

- `entity_type` (string): Entity whose fields to list: leads, contacts, or companies. Default "leads".

Output parameters:

- `items` (array): Returned entities.

### `create_custom_field` (~160 tokens)

Create a custom field on leads, contacts, or companies. Not idempotent: each call creates another field, so check list_custom_fields first. Returns the created field. Clears the custom-field cache for that entity. Provide enum_values for select-type fields.

Input parameters:

- `entity_type` (string, required): Entity to add the field to: leads, contacts, or companies.
- `enum_values` (array): Option labels for select or multiselect fields, in display order, e.g. ["Low", "High"]. Ignored by other types.
- `field_type` (string, required): Kommo field type sent as-is, e.g. text, numeric, select, multiselect, date, url, checkbox.
- `name` (string, required): Field display name.

Output parameters:

- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `account_id` (integer|null): Kommo account ID.
- `code` (string|null): System field code, or null.
- `entity_type` (string|null): Entity the field belongs to.
- `enums` (array|null): Options for select-like fields.
- `id` (integer): Field ID.
- `is_api_only` (boolean|null): Whether the field is API only.
- `name` (string|null): Field name.
- `sort` (integer|null): Sort order.
- `type` (string|null): Field type, e.g. text, select.

### `create_company` (~72 tokens)

Create a company record with a name only. Not idempotent: duplicates are not checked, so look with list_companies first. Returns the created company. To create a company alongside a new lead, use create_lead_complex.

Input parameters:

- `name` (string, required): Company name, e.g. "Acme Inc".

Output parameters:

- `_embedded` (object): Embedded tags and leads.
- `_links` (object): HAL links as returned by Kommo (self, next, ...).
- `account_id` (integer|null): Kommo account ID.
- `closest_task_at` (integer|null): Next task deadline, Unix seconds, or null.
- `created_at` (integer|null): Creation time, Unix seconds.
- `created_by` (integer|null): ID of the user who created it.
- `custom_fields_values` (array|null): Custom field values in Kommo format: objects with field_id, field_code and values.
- `group_id` (integer|null): ID of the responsible user's group.
- `id` (integer): Company ID.
- `name` (string|null): Company name.
- `responsible_user_id` (integer|null): ID of the responsible Kommo user.
- `updated_at` (integer|null): Last update time, Unix seconds.
- `updated_by` (integer|null): ID of the user who last updated it.

### `list_companies` (~113 tokens)

List companies. Read-only. Returns an array of up to `limit` companies (max 250); pass `page` for paginated output with a has_next flag. No name search.

Input parameters:

- `limit` (integer): Companies per page. Default 50, capped at 250.
- `page` (integer): 1-based page number. Omit for a plain array (first page). When set, returns {items, page, limit, has_next}; request page+1 while has_next is true.

Output parameters:

- `has_next` (boolean): True when another page exists (only when paginated).
- `items` (array): Returned entities.
- `limit` (integer): Page size used (only when `page` was requested).
- `page` (integer): Page number returned (only when `page` was requested).

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/depper-ia-kommo-kiro-power/kommo-kiro-power#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 65
- 2026-11-19: 80
- 2026-11-18: 64
- 2026-11-17: 65
- 2026-11-16: 65
- 2026-11-15: 65
- 2026-11-14: 80
- 2026-11-13: 80
- 2026-11-12: 65
- 2026-11-11: 64
- 2026-11-10: 64
- 2026-11-09: 63
- 2026-11-08: 78
- 2026-11-07: 80
- 2026-11-06: 65
- 2026-11-05: 65
- 2026-11-04: 80
- 2026-11-03: 65
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78
- 2026-10-28: 77
- 2026-10-27: 62
- 2026-10-26: 61
- 2026-10-25: 61
- 2026-10-24: 75
- 2026-10-23: 75

## Common questions

### What is the Kommo CRM MCP server?

Kommo CRM is an MCP server listed in the public MCP registry as io.github.depper-IA/kommo-kiro-power. Manage Kommo CRM leads, contacts, pipelines, tasks, notes, tags and companies. This page covers its PyPI package (kommo-kiro-power).

### Is the Kommo CRM MCP server safe to use?

Kommo CRM scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Kommo CRM MCP server expose?

Kommo CRM exposes 30 tools: list_leads, get_lead, create_lead, update_lead, delete_lead, and 25 more. Their descriptions and schemas cost roughly 3,755 tokens of context every time the server is loaded.

### Is the Kommo CRM MCP server still maintained?

Kommo CRM is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Kommo CRM MCP server under?

Kommo CRM declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Kommo CRM MCP server?

VerifyMCP ran 15 checks on Kommo CRM, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Kommo CRM: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/kommo-kiro-power/
- Socket report: https://socket.dev/pypi/package/kommo-kiro-power
- Changelog RSS feed: https://verifymcp.io/servers/depper-ia-kommo-kiro-power/kommo-kiro-power.xml
- Changelog JSON feed: https://verifymcp.io/servers/depper-ia-kommo-kiro-power/kommo-kiro-power/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/depper-ia-kommo-kiro-power/kommo-kiro-power.json
- HTML version of this page: https://verifymcp.io/servers/depper-ia-kommo-kiro-power/kommo-kiro-power
