Skip to main content
Glama
Kommo Kiro MCP

Kommo Kiro MCP

kommo-kiro-power — Kommo CRM Power for Kiro

Connect AI agents to your Kommo CRM (formerly amoCRM) using the Model Context Protocol. Manage leads, contacts, pipelines, tasks, notes, tags, and companies — all from natural language in Kiro or any MCP-compatible client.

Features

Category

Tools

Leads

list, get, create, update, delete, move stage, bulk update

Contacts

list, get, create, update

Pipelines

list, create, update

Stages

list, create, update

Tags

list, add, remove (auto-creates if needed)

Tasks

create, list (with overdue filter)

Notes

add note to lead

Chat

list templates, send message

Companies

create, list

Custom Fields

list, create (text, select, multiselect, date, etc.)

Advanced

create lead + contact + company in one call

Related MCP server: Kommo MCP Server

Quick Start

Install as Kiro Power

  1. Open Kiro → Powers panel → Add Custom Power

  2. Select Import power from GitHub

  3. Paste: https://github.com/depper-IA/kommo-kiro-power

  4. Follow the onboarding steps when activated

Install as standalone MCP

Published on PyPI and the official MCP Registry. With uv installed, no clone is needed:

uvx --from kommo-kiro-power kommo-mcp

Or install the one-click MCPB bundle (kommo-crm.mcpb) in Claude Desktop or any MCPB-compatible client. Bundle sources live in mcpb/. After changing tools, run python scripts/build_mcpb.py to sync the manifest, then pnpm dlx @anthropic-ai/mcpb pack mcpb kommo-crm.mcpb. For Smithery, python scripts/build_mcpb.py --smithery kommo-crm-smithery.mcpb builds a variant that also carries each tool's inputSchema.

Or from source:

git clone https://github.com/depper-IA/kommo-kiro-power.git
cd kommo-kiro-power
pip install -e .

Setup

1. Create a Kommo Integration

  1. Go to Kommo → Settings → Integrations → Create integration

  2. Copy the Client ID and Client Secret

  3. Set http://localhost:8080/callback as the Redirect URI

2. Configure Credentials

cp .env.example .env
# Edit .env with your Kommo integration details

3. Authenticate (OAuth)

python scripts/oauth_setup.py

A browser opens → sign in to Kommo → authorize → tokens saved automatically.

4. Run the MCP Server

python -m kommo_mcp
# or
kommo-mcp

Usage with Kiro

Once installed as a Power, the server activates automatically when you mention keywords like "kommo", "leads", "pipeline", "crm", or "contacts" in your conversation.

"Show me all leads in the Sales pipeline"
"Create a lead for Maria from TechCorp with phone +57 310 543 6281"
"Move lead 12345 to the Negotiation stage"
"List all overdue tasks"

Usage with Other MCP Clients

Add to your claude_desktop_config.json, opencode.json, or equivalent:

{
  "mcpServers": {
    "kommo": {
      "command": "uvx",
      "args": ["--from", "kommo-kiro-power", "kommo-mcp"],
      "env": {
        "KOMMO_SUBDOMAIN": "your_subdomain",
        "KOMMO_ACCESS_TOKEN": "your_access_token"
      }
    }
  }
}

Architecture

kommo-kiro-power/
├── plugin.json           # Kiro Power manifest (Agent Plugins format)
├── POWER.md              # Legacy Kiro Power metadata + onboarding
├── mcp.json              # MCP server config for Kiro
├── server.json           # Official MCP Registry metadata
├── skills/               # Workflow guides loaded on-demand
│   ├── leads-workflow/SKILL.md
│   ├── pipeline-management/SKILL.md
│   └── automation-patterns/SKILL.md
├── kommo_mcp/            # Python MCP server
│   ├── __main__.py       # Entry point (stdio transport)
│   ├── mcp_server.py     # Server + tool registration
│   ├── kommo_client.py   # HTTP client (OAuth, retry, cache)
│   └── tools/            # Tool definitions + handlers
│       ├── leads.py
│       ├── contacts.py
│       └── pipelines.py
├── scripts/
│   └── oauth_setup.py    # One-time OAuth authentication
├── pyproject.toml        # Package config
└── requirements.txt

Security

  • Credentials read from .env — never hardcoded

  • .env is in .gitignore — never committed

  • OAuth v4 with automatic token refresh

  • Rate limiting: max 5 requests/second

  • Exponential backoff with jitter on failures

  • Response caching for pipelines/stages/fields (10 min TTL)

Compatibility

  • Python: 3.10, 3.11, 3.12, 3.13

  • MCP Clients: Kiro, Claude Desktop, OpenCode, Cursor, Codex

  • Kommo API: v4

Privacy

The server runs locally on your machine and talks only to your own Kommo account API. It has no telemetry and sends no data to the author or any third party. See PRIVACY.md.

Support

License

MIT

Available Tools

30 tools
add_noteA

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.

Inputs: text (required), lead_id (required). Returns: The created note.

add_tagA
Idempotent

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.

Inputs: lead_id (required), tag_name (required). Returns: The lead after the tag was added.

bulk_update_leadsA
Idempotent

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.

Inputs: leads_updates (required). Returns: Kommo bulk update response: the updated leads (usually id, name, updated_at) un…

create_companyA

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.

Inputs: name (required). Returns: The created company.

create_contactA

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.

Inputs: name (required), email, phone. Returns: The created contact (id, name and request_id at minimum).

create_custom_fieldA

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.

Inputs: name (required), field_type (required), entity_type (required), enum_values. Returns: The created custom field.

create_leadA

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.

Inputs: name (required), tags, price, stage_id, +3 more. Returns: The created lead (id, name and request_id at minimum).

create_lead_complexA

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.

Inputs: name (required), tags, stage_id, pipeline_id, +5 more. Returns: Result of POST /leads/complex for the created (or merged) lead.

create_pipelineA

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.

Inputs: name (required). Returns: The created pipeline.

create_stageA

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.

Inputs: name (required), pipeline_id (required), color. Returns: The created stage.

create_taskA

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.

Inputs: text (required), lead_id (required), due_date (required), responsible_user_id. Returns: The created task.

delete_leadA
DestructiveIdempotent

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.

Inputs: lead_id (required). Returns: The lead marked as deleted, as returned by Kommo.

get_contactA
Read-onlyIdempotent

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.

Inputs: contact_id (required). Returns: The contact with tags and custom fields.

get_leadA
Read-onlyIdempotent

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.

Inputs: lead_id (required). Returns: The lead with contacts, tags and custom fields.

list_chat_templatesA
Read-onlyIdempotent

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

Inputs: no named parameters. Returns: Chat templates, as {items: [...]}.

list_companiesA
Read-onlyIdempotent

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.

Inputs: page, limit. Returns: Companies, as {items: [company, ...]}. With `page` set, also page, limit and ha…

list_contactsA
Read-onlyIdempotent

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.

Inputs: page, limit, query. Returns: Contacts, as {items: [contact, ...]}. With `page` set, also page, limit and has…

list_custom_fieldsA
Read-onlyIdempotent

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.

Inputs: entity_type. Returns: Custom fields, as {items: [field, ...]}.

list_leadsA
Read-onlyIdempotent

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.

Inputs: limit, stage_id, pipeline_id. Returns: Leads, as {items: [lead, ...]}.

list_pipelinesA
Read-onlyIdempotent

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.

Inputs: no named parameters. Returns: Pipelines, as {items: [pipeline, ...]}.

list_stagesA
Read-onlyIdempotent

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.

Inputs: pipeline_id (required). Returns: Stages of the pipeline, as {items: [stage, ...]}.

list_tagsA
Read-onlyIdempotent

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.

Inputs: entity_type. Returns: Tags, as {items: [tag, ...]}.

list_tasksA
Read-onlyIdempotent

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.

Inputs: page, limit, lead_id, filter_overdue. Returns: Tasks, as {items: [task, ...]}. With `page` set, also page, limit and has_next.

move_lead_stageA
Idempotent

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.

Inputs: lead_id (required), stage_id (required), pipeline_id. Returns: The lead after the stage change.

remove_tagA
Idempotent

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.

Inputs: lead_id (required), tag_name (required). Returns: The lead after the tag was removed (unchanged if absent).

send_chat_messageA

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.

Inputs: text (required), lead_id (required). Returns: Kommo response to POST /talks/{talk_id}/send_message, passed through unchanged.

update_contactA
Idempotent

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.

Inputs: fields (required), contact_id (required). Returns: The updated contact as returned by Kommo.

update_leadA
Idempotent

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.

Inputs: fields (required), lead_id (required). Returns: The updated lead as returned by Kommo.

update_pipelineA
Idempotent

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.

Inputs: name (required), pipeline_id (required). Returns: The updated pipeline.

update_stageA
Idempotent

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.

Inputs: stage_id (required), pipeline_id (required), name, sort, +1 more. Returns: The updated stage.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 30 tools

    Disambiguation5/5

    Every tool targets a distinct entity+action, and the descriptions proactively resolve the few natural overlaps (update_lead vs move_lead_stage vs bulk_update_leads, create_lead vs create_lead_complex, add_note vs send_chat_message). Cross-references like 'use X instead of Y' make selection unambiguous. No two tools appear to do the same thing.

    Naming Consistency5/5

    Consistent verb_noun snake_case throughout (create_lead, update_lead, delete_lead, list_leads, create_stage, update_pipeline, add_tag, remove_tag, send_chat_message). Pluralization is applied sensibly for list operations. No mixed conventions or vague verbs.

    Tool Count4/5

    30 tools is on the heavy side, but the domain genuinely spans leads, contacts, companies, pipelines, stages, tasks, tags, notes, chat, and custom fields, so most tools earn their place. It is comprehensive rather than padded, though a few operations could be consolidated.

    Completeness3/5

    Leads have full lifecycle coverage (create/get/list/update/delete/move/bulk), but other entities are partial: contacts lack delete, companies have only create/list (no get/update/delete), tasks lack get/update/delete, and pipelines/stages/custom fields lack delete/update in places. These gaps will force workarounds for maintenance workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables integration with Kommo CRM to manage leads, add notes and tasks, update custom fields, and list pipelines. Supports multi-tenant authentication and includes an approval system for bulk operations.
      2
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to autonomously interact with Kommo CRM, providing tools for managing pipelines, leads, contacts, and custom fields via the Kommo API v4.
      27
      1
      -
    • A
      license
      C
      quality
      D
      maintenance
      Enables AI agents to manage Kommo CRM (formerly AmoCRM) entities including leads, contacts, companies, tasks, notes, pipelines, and products through natural language commands via the Model Context Protocol.
      39
      26 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      AI-powered CRM assistant for Kommo/amoCRM that provides natural language management via Telegram bot and MCP protocol, enabling analytics, entity operations, and CRM setup.
      8
      -