Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Kommo CRM

PYPI · KOMMO-KIRO-POWER

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

Available components

−15 this week 65 Trust /100

Last scanned (10 hours ago)

Scores higher than 57% of PyPI servers

Category CRM and Sales

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 19 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 15 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 13 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 +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.

  • 9 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/kommo-kiro-power@1.0.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 30 exposed · ~3,755 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_note ~96

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.

NameTypeReqDescription
lead_idintegeryesKommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
textstringyesNote content (plain text).
NameTypeReqDescription
_linksobject–HAL links as returned by Kommo (self, next, ...).
account_idinteger|null–Kommo account ID.
created_atinteger|null–Creation time, Unix seconds.
created_byinteger|null–ID of the user who created it.
entity_idinteger|null–ID of the entity the note is attached to.
group_idinteger|null–ID of the responsible user's group.
idinteger–Note ID.
note_typestring|null–Note type, e.g. common.
paramsobject–Note parameters, e.g. {text}.
responsible_user_idinteger|null–ID of the responsible Kommo user.
updated_atinteger|null–Last update time, Unix seconds.
updated_byinteger|null–ID of the user who last updated it.

No examples provided.

add_tag ~114

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.

NameTypeReqDescription
lead_idintegeryesKommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
tag_namestringyesExact tag name (case-sensitive), e.g. "vip".
NameTypeReqDescription
_embeddedobject–Embedded tags, contacts and companies.
_linksobject–HAL links as returned by Kommo (self, next, ...).
account_idinteger|null–Kommo account ID.
closed_atinteger|null–Closing time, Unix seconds, or null.
closest_task_atinteger|null–Next task deadline, Unix seconds, or null.
created_atinteger|null–Creation time, Unix seconds.
created_byinteger|null–ID of the user who created it.
custom_fields_valuesarray|null–Custom field values in Kommo format: objects with field_id, field_code and values.
group_idinteger|null–ID of the responsible user's group.
idinteger–Lead ID.
is_deletedboolean|null–Whether the lead is deleted.
loss_reason_idinteger|null–Loss reason ID, or null.
namestring|null–Lead name.
pipeline_idinteger|null–Pipeline ID.
priceinteger|null–Lead budget.
responsible_user_idinteger|null–ID of the responsible Kommo user.
status_idinteger|null–Current stage ID.
updated_atinteger|null–Last update time, Unix seconds.
updated_byinteger|null–ID of the user who last updated it.

No examples provided.

bulk_update_leads ~98

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.

NameTypeReqDescription
leads_updatesarrayyesUpdates to apply, one per lead. Example: [{"id": 123, "fields": {"status_id": 456}}].
NameTypeReqDescription
_embeddedobject–Updated leads.
_linksobject–HAL links as returned by Kommo (self, next, ...).
_total_itemsinteger–Number of leads updated.

No examples provided.

create_company ~72

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.

NameTypeReqDescription
namestringyesCompany name, e.g. "Acme Inc".
NameTypeReqDescription
_embeddedobject–Embedded tags and leads.
_linksobject–HAL links as returned by Kommo (self, next, ...).
account_idinteger|null–Kommo account ID.
closest_task_atinteger|null–Next task deadline, Unix seconds, or null.
created_atinteger|null–Creation time, Unix seconds.
created_byinteger|null–ID of the user who created it.
custom_fields_valuesarray|null–Custom field values in Kommo format: objects with field_id, field_code and values.
group_idinteger|null–ID of the responsible user's group.
idinteger–Company ID.
namestring|null–Company name.
responsible_user_idinteger|null–ID of the responsible Kommo user.
updated_atinteger|null–Last update time, Unix seconds.
updated_byinteger|null–ID of the user who last updated it.

No examples provided.

create_contact ~116

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.

NameTypeReqDescription
emailstring–Email address, e.g. jane@example.com.
namestringyesContact full name.
phonestring–Phone number, ideally international, e.g. +15551234567.
NameTypeReqDescription
_embeddedobject–Embedded tags and companies.
_linksobject–HAL links as returned by Kommo (self, next, ...).
account_idinteger|null–Kommo account ID.
closest_task_atinteger|null–Next task deadline, Unix seconds, or null.
created_atinteger|null–Creation time, Unix seconds.
created_byinteger|null–ID of the user who created it.
custom_fields_valuesarray|null–Custom field values in Kommo format: objects with field_id, field_code and values.
first_namestring|null–First name.
group_idinteger|null–ID of the responsible user's group.
idinteger–Contact ID.
last_namestring|null–Last name.
namestring|null–Full name.
responsible_user_idinteger|null–ID of the responsible Kommo user.
updated_atinteger|null–Last update time, Unix seconds.
updated_byinteger|null–ID of the user who last updated it.

No examples provided.

create_custom_field ~160

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.

NameTypeReqDescription
entity_typestringyesEntity to add the field to: leads, contacts, or companies.
enum_valuesarray–Option labels for select or multiselect fields, in display order, e.g. ["Low", "High"]. Ignored by other types.
field_typestringyesKommo field type sent as-is, e.g. text, numeric, select, multiselect, date, url, checkbox.
namestringyesField display name.
NameTypeReqDescription
_linksobject–HAL links as returned by Kommo (self, next, ...).
account_idinteger|null–Kommo account ID.
codestring|null–System field code, or null.
entity_typestring|null–Entity the field belongs to.
enumsarray|null–Options for select-like fields.
idinteger–Field ID.
is_api_onlyboolean|null–Whether the field is API only.
namestring|null–Field name.
sortinteger|null–Sort order.
typestring|null–Field type, e.g. text, select.

No examples provided.

create_lead ~294

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.

NameTypeReqDescription
custom_fields_valuesarray–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…
namestringyesLead name (title of the deal).
pipeline_idinteger–Pipeline to create the lead in. Get IDs from list_pipelines. Omit to use the account default.
pricenumber–Deal value in the account currency, e.g. 1500.
responsible_user_idinteger–Kommo user ID to assign as owner. Omit for the default user.
stage_idinteger–Stage (status) to place the lead in. Get IDs from list_stages. Omit for the first stage of the pipeline.
tagsarray–Tag names to attach, e.g. ["vip", "web"]. Created if missing.
NameTypeReqDescription
_embeddedobject–Embedded tags, contacts and companies.
_linksobject–HAL links as returned by Kommo (self, next, ...).
account_idinteger|null–Kommo account ID.
closed_atinteger|null–Closing time, Unix seconds, or null.
closest_task_atinteger|null–Next task deadline, Unix seconds, or null.
created_atinteger|null–Creation time, Unix seconds.
created_byinteger|null–ID of the user who created it.
custom_fields_valuesarray|null–Custom field values in Kommo format: objects with field_id, field_code and values.
group_idinteger|null–ID of the responsible user's group.
idinteger–Lead ID.
is_deletedboolean|null–Whether the lead is deleted.
loss_reason_idinteger|null–Loss reason ID, or null.
namestring|null–Lead name.
pipeline_idinteger|null–Pipeline ID.
priceinteger|null–Lead budget.
responsible_user_idinteger|null–ID of the responsible Kommo user.
status_idinteger|null–Current stage ID.
updated_atinteger|null–Last update time, Unix seconds.
updated_byinteger|null–ID of the user who last updated it.

No examples provided.

create_lead_complex ~318

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.

NameTypeReqDescription
company_namestring–Name of a new company to create and attach.
contact_emailstring–Contact email address.
contact_namestring–Name of a new contact to create. Phone and email are ignored unless this is set.
contact_phonestring–Contact phone number, e.g. +15551234567.
custom_fields_valuesarray–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…
namestringyesLead name (title of the deal).
pipeline_idinteger–Pipeline for the lead. Get IDs from list_pipelines.
stage_idinteger–Stage for the lead. Get IDs from list_stages.
tagsarray–Tag names to attach to the lead. Created if missing.
NameTypeReqDescription
company_idinteger|null–ID of the created or linked company.
contact_idinteger|null–ID of the created or linked contact.
idintegeryesLead ID.
mergedboolean–True when Kommo merged the lead into an existing duplicate.
request_idarray–Request IDs sent for this lead.

No examples provided.

create_pipeline ~66

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.

NameTypeReqDescription
namestringyesPipeline name, e.g. "Enterprise".
NameTypeReqDescription
_embeddedobject–Embedded resources.
account_idinteger|null–Kommo account ID.
idinteger–Pipeline ID.
is_archiveboolean|null–Whether the pipeline is archived.
is_mainboolean|null–Whether this is the main pipeline.
is_unsorted_onboolean|null–Whether the Incoming leads stage is enabled.
namestring|null–Pipeline name.
sortinteger|null–Sort order.

No examples provided.

create_stage ~126

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.

NameTypeReqDescription
colorstring–Hex color sent to Kommo as-is, e.g. #4CAF50. Optional; Kommo may restrict it to its own palette.
namestringyesStage name, e.g. "Negotiation".
pipeline_idintegeryesKommo pipeline ID (integer). Obtain it from list_pipelines.
NameTypeReqDescription
account_idinteger|null–Kommo account ID.
colorstring|null–Hex color.
idinteger–Stage ID.
is_editableboolean|null–Whether the stage can be edited.
namestring|null–Stage name.
pipeline_idinteger|null–Parent pipeline ID.
sortinteger|null–Sort order.
typeinteger|null–0 for regular stages, 1 for unsorted.

No examples provided.

create_task ~144

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.

NameTypeReqDescription
due_dateintegeryesDeadline as a Unix timestamp in seconds, e.g. 1767225600.
lead_idintegeryesKommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
responsible_user_idinteger–Kommo user ID responsible for the task. Omit for the default.
textstringyesTask description shown in Kommo.
NameTypeReqDescription
_linksobject–HAL links as returned by Kommo (self, next, ...).
account_idinteger|null–Kommo account ID.
complete_tillinteger|null–Deadline, Unix seconds.
created_atinteger|null–Creation time, Unix seconds.
created_byinteger|null–ID of the user who created it.
durationinteger|null–Duration in seconds.
entity_idinteger|null–ID of the entity the task is attached to.
entity_typestring|null–Entity type, e.g. leads.
group_idinteger|null–ID of the responsible user's group.
idinteger–Task ID.
is_completedboolean|null–Whether the task is completed.
responsible_user_idinteger|null–ID of the responsible Kommo user.
result––Completion result (object or array), may be empty.
task_type_idinteger|null–Task type ID (1 is follow-up).
textstring|null–Task description.
updated_atinteger|null–Last update time, Unix seconds.
updated_byinteger|null–ID of the user who last updated it.

No examples provided.

delete_lead ~90

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.

NameTypeReqDescription
lead_idintegeryesKommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
NameTypeReqDescription
_embeddedobject–Embedded tags, contacts and companies.
_linksobject–HAL links as returned by Kommo (self, next, ...).
account_idinteger|null–Kommo account ID.
closed_atinteger|null–Closing time, Unix seconds, or null.
closest_task_atinteger|null–Next task deadline, Unix seconds, or null.
created_atinteger|null–Creation time, Unix seconds.
created_byinteger|null–ID of the user who created it.
custom_fields_valuesarray|null–Custom field values in Kommo format: objects with field_id, field_code and values.
group_idinteger|null–ID of the responsible user's group.
idinteger–Lead ID.
is_deletedboolean|null–Whether the lead is deleted.
loss_reason_idinteger|null–Loss reason ID, or null.
namestring|null–Lead name.
pipeline_idinteger|null–Pipeline ID.
priceinteger|null–Lead budget.
responsible_user_idinteger|null–ID of the responsible Kommo user.
status_idinteger|null–Current stage ID.
updated_atinteger|null–Last update time, Unix seconds.
updated_byinteger|null–ID of the user who last updated it.

No examples provided.

get_contact ~69

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.

NameTypeReqDescription
contact_idintegeryesKommo contact ID (integer). Obtain it from list_contacts or from the create_contact result.
NameTypeReqDescription
_embeddedobject–Embedded tags and companies.
_linksobject–HAL links as returned by Kommo (self, next, ...).
account_idinteger|null–Kommo account ID.
closest_task_atinteger|null–Next task deadline, Unix seconds, or null.
created_atinteger|null–Creation time, Unix seconds.
created_byinteger|null–ID of the user who created it.
custom_fields_valuesarray|null–Custom field values in Kommo format: objects with field_id, field_code and values.
first_namestring|null–First name.
group_idinteger|null–ID of the responsible user's group.
idinteger–Contact ID.
last_namestring|null–Last name.
namestring|null–Full name.
responsible_user_idinteger|null–ID of the responsible Kommo user.
updated_atinteger|null–Last update time, Unix seconds.
updated_byinteger|null–ID of the user who last updated it.

No examples provided.

get_lead ~74

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.

NameTypeReqDescription
lead_idintegeryesKommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
NameTypeReqDescription
_embeddedobject–Embedded tags, contacts and companies.
_linksobject–HAL links as returned by Kommo (self, next, ...).
account_idinteger|null–Kommo account ID.
closed_atinteger|null–Closing time, Unix seconds, or null.
closest_task_atinteger|null–Next task deadline, Unix seconds, or null.
created_atinteger|null–Creation time, Unix seconds.
created_byinteger|null–ID of the user who created it.
custom_fields_valuesarray|null–Custom field values in Kommo format: objects with field_id, field_code and values.
group_idinteger|null–ID of the responsible user's group.
idinteger–Lead ID.
is_deletedboolean|null–Whether the lead is deleted.
loss_reason_idinteger|null–Loss reason ID, or null.
namestring|null–Lead name.
pipeline_idinteger|null–Pipeline ID.
priceinteger|null–Lead budget.
responsible_user_idinteger|null–ID of the responsible Kommo user.
status_idinteger|null–Current stage ID.
updated_atinteger|null–Last update time, Unix seconds.
updated_byinteger|null–ID of the user who last updated it.

No examples provided.

list_chat_templates ~48

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).

Input schema present but exposes no named parameters.

NameTypeReqDescription
itemsarrayyesReturned entities.

No examples provided.

list_companies ~113

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.

NameTypeReqDescription
limitinteger–Companies per page. Default 50, capped at 250.
pageinteger–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.
NameTypeReqDescription
has_nextboolean–True when another page exists (only when paginated).
itemsarrayyesReturned entities.
limitinteger–Page size used (only when `page` was requested).
pageinteger–Page number returned (only when `page` was requested).

No examples provided.

list_contacts ~182

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.

NameTypeReqDescription
limitinteger–Contacts per page. Default 50, capped at 250.
pageinteger–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.
querystring–Free-text search matched by Kommo against name, phone, and email, e.g. "Jane" or "+15551234567". Omit to list without filtering.
NameTypeReqDescription
has_nextboolean–True when another page exists (only when paginated).
itemsarrayyesReturned entities.
limitinteger–Page size used (only when `page` was requested).
pageinteger–Page number returned (only when `page` was requested).

No examples provided.

list_custom_fields ~88

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.

NameTypeReqDescription
entity_typestring–Entity whose fields to list: leads, contacts, or companies. Default "leads".
NameTypeReqDescription
itemsarrayyesReturned entities.

No examples provided.

list_leads ~131

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.

NameTypeReqDescription
limitinteger–Maximum number of leads to return. Default 50.
pipeline_idinteger–Only leads in this pipeline. Get IDs from list_pipelines.
stage_idinteger–Only leads in this stage. Ignored unless pipeline_id is also set. Get IDs from list_stages.
NameTypeReqDescription
itemsarrayyesReturned entities.

No examples provided.

list_pipelines ~70

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
itemsarrayyesReturned entities.

No examples provided.

list_stages ~87

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.

NameTypeReqDescription
pipeline_idintegeryesKommo pipeline ID (integer). Obtain it from list_pipelines.
NameTypeReqDescription
itemsarrayyesReturned entities.

No examples provided.

list_tags ~77

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.

NameTypeReqDescription
entity_typestring–Which tag set to list: leads, contacts or companies (singular forms accepted). Default "lead".
NameTypeReqDescription
itemsarrayyesReturned entities.

No examples provided.

list_tasks ~179

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.

NameTypeReqDescription
filter_overdueboolean–If true, only uncompleted tasks whose deadline has passed.
lead_idinteger–Only tasks attached to this lead. Omit for all tasks.
limitinteger–Tasks per page, max 250. Omit for Kommo's default (50).
pageinteger–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.
NameTypeReqDescription
has_nextboolean–True when another page exists (only when paginated).
itemsarrayyesReturned entities.
limitinteger–Page size used (only when `page` was requested).
pageinteger–Page number returned (only when `page` was requested).

No examples provided.

move_lead_stage ~130

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.

NameTypeReqDescription
lead_idintegeryesKommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
pipeline_idinteger–Target pipeline ID. Only needed when the stage belongs to a different pipeline than the lead's current one.
stage_idintegeryesTarget stage ID. Get IDs from list_stages.
NameTypeReqDescription
_embeddedobject–Embedded tags, contacts and companies.
_linksobject–HAL links as returned by Kommo (self, next, ...).
account_idinteger|null–Kommo account ID.
closed_atinteger|null–Closing time, Unix seconds, or null.
closest_task_atinteger|null–Next task deadline, Unix seconds, or null.
created_atinteger|null–Creation time, Unix seconds.
created_byinteger|null–ID of the user who created it.
custom_fields_valuesarray|null–Custom field values in Kommo format: objects with field_id, field_code and values.
group_idinteger|null–ID of the responsible user's group.
idinteger–Lead ID.
is_deletedboolean|null–Whether the lead is deleted.
loss_reason_idinteger|null–Loss reason ID, or null.
namestring|null–Lead name.
pipeline_idinteger|null–Pipeline ID.
priceinteger|null–Lead budget.
responsible_user_idinteger|null–ID of the responsible Kommo user.
status_idinteger|null–Current stage ID.
updated_atinteger|null–Last update time, Unix seconds.
updated_byinteger|null–ID of the user who last updated it.

No examples provided.

remove_tag ~125

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.

NameTypeReqDescription
lead_idintegeryesKommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
tag_namestringyesExact tag name (case-sensitive) to detach, e.g. "vip".
NameTypeReqDescription
_embeddedobject–Embedded tags, contacts and companies.
_linksobject–HAL links as returned by Kommo (self, next, ...).
account_idinteger|null–Kommo account ID.
closed_atinteger|null–Closing time, Unix seconds, or null.
closest_task_atinteger|null–Next task deadline, Unix seconds, or null.
created_atinteger|null–Creation time, Unix seconds.
created_byinteger|null–ID of the user who created it.
custom_fields_valuesarray|null–Custom field values in Kommo format: objects with field_id, field_code and values.
group_idinteger|null–ID of the responsible user's group.
idinteger–Lead ID.
is_deletedboolean|null–Whether the lead is deleted.
loss_reason_idinteger|null–Loss reason ID, or null.
namestring|null–Lead name.
pipeline_idinteger|null–Pipeline ID.
priceinteger|null–Lead budget.
responsible_user_idinteger|null–ID of the responsible Kommo user.
status_idinteger|null–Current stage ID.
updated_atinteger|null–Last update time, Unix seconds.
updated_byinteger|null–ID of the user who last updated it.

No examples provided.

send_chat_message ~113

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.

NameTypeReqDescription
lead_idintegeryesID of a lead that already has an active conversation. Get it from list_leads.
textstringyesMessage text sent to the customer.

Structured output declared, but exposes no named fields.

No examples provided.

update_contact ~148

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.

NameTypeReqDescription
contact_idintegeryesKommo contact ID (integer). Obtain it from list_contacts or from the create_contact result.
fieldsobjectyesRaw 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}]}…
NameTypeReqDescription
_embeddedobject–Embedded tags and companies.
_linksobject–HAL links as returned by Kommo (self, next, ...).
account_idinteger|null–Kommo account ID.
closest_task_atinteger|null–Next task deadline, Unix seconds, or null.
created_atinteger|null–Creation time, Unix seconds.
created_byinteger|null–ID of the user who created it.
custom_fields_valuesarray|null–Custom field values in Kommo format: objects with field_id, field_code and values.
first_namestring|null–First name.
group_idinteger|null–ID of the responsible user's group.
idinteger–Contact ID.
last_namestring|null–Last name.
namestring|null–Full name.
responsible_user_idinteger|null–ID of the responsible Kommo user.
updated_atinteger|null–Last update time, Unix seconds.
updated_byinteger|null–ID of the user who last updated it.

No examples provided.

update_lead ~189

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.

NameTypeReqDescription
fieldsobjectyesRaw 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_idintegeryesKommo lead ID (integer). Obtain it from list_leads or from the create_lead result.
NameTypeReqDescription
_embeddedobject–Embedded tags, contacts and companies.
_linksobject–HAL links as returned by Kommo (self, next, ...).
account_idinteger|null–Kommo account ID.
closed_atinteger|null–Closing time, Unix seconds, or null.
closest_task_atinteger|null–Next task deadline, Unix seconds, or null.
created_atinteger|null–Creation time, Unix seconds.
created_byinteger|null–ID of the user who created it.
custom_fields_valuesarray|null–Custom field values in Kommo format: objects with field_id, field_code and values.
group_idinteger|null–ID of the responsible user's group.
idinteger–Lead ID.
is_deletedboolean|null–Whether the lead is deleted.
loss_reason_idinteger|null–Loss reason ID, or null.
namestring|null–Lead name.
pipeline_idinteger|null–Pipeline ID.
priceinteger|null–Lead budget.
responsible_user_idinteger|null–ID of the responsible Kommo user.
status_idinteger|null–Current stage ID.
updated_atinteger|null–Last update time, Unix seconds.
updated_byinteger|null–ID of the user who last updated it.

No examples provided.

update_pipeline ~76

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.

NameTypeReqDescription
namestringyesNew pipeline name.
pipeline_idintegeryesKommo pipeline ID (integer). Obtain it from list_pipelines.
NameTypeReqDescription
_embeddedobject–Embedded resources.
account_idinteger|null–Kommo account ID.
idinteger–Pipeline ID.
is_archiveboolean|null–Whether the pipeline is archived.
is_mainboolean|null–Whether this is the main pipeline.
is_unsorted_onboolean|null–Whether the Incoming leads stage is enabled.
namestring|null–Pipeline name.
sortinteger|null–Sort order.

No examples provided.

update_stage ~162

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.

NameTypeReqDescription
colorstring–New hex color, e.g. #4CAF50, sent to Kommo as-is.
namestring–New stage name.
pipeline_idintegeryesKommo pipeline ID (integer). Obtain it from list_pipelines.
sortinteger–New sort position; lower values appear first (e.g. 10, 20).
stage_idintegeryesStage ID within that pipeline. Obtain it from list_stages.
NameTypeReqDescription
account_idinteger|null–Kommo account ID.
colorstring|null–Hex color.
idinteger–Stage ID.
is_editableboolean|null–Whether the stage can be edited.
namestring|null–Stage name.
pipeline_idinteger|null–Parent pipeline ID.
sortinteger|null–Sort order.
typeinteger|null–0 for regular stages, 1 for unsorted.

No examples provided.

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.

pypi · kommo-kiro-power

# add to Claude Code
claude mcp add depper-ia-kommo-kiro-power -- uvx kommo-kiro-power
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.