Integration

Kommo integration

Kommo CRM, formerly amoCRM, through its REST v4 API. Read and write the sales pipeline: leads, contacts, companies, tasks and notes, plus the account metadata that gives them meaning (pipelines and their stages, custom field definitions, users and tags). Every account lives on its own subdomain, so the subdomain is part of the connection. Responses are HAL documents: collections arrive under _embedded and writes echo back only the identifiers they touched.

Connect Kommo How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Kommo.Built from the 19 Kommo tools below, on the connection you add once.

Common Kommo use cases

reporting on open deals per stage
advancing a deal to the next stage
mapping a stage name to a status_id
reading a contact before enriching it
creating the account behind a new deal
registering a new customer from a signup
writing an agent summary back onto a deal
resolving a tag name before tagging a deal
building a daily task digest for a sales rep
creating a call back task when a deal stalls

What you can do with Kommo

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Contact, 4 operations

create_contactsCreate contactsPOSTCreates contacts from an array of contact objects and returns the new identifiers.
get_contactGet contactGETReturns a single contact as a bare object, without the collection envelope.
list_contactsList contactsGETReturns a page of contacts under _embedded.contacts.
update_contactUpdate contactPATCHApplies a partial update to a single contact and returns its id and new updated_at.

Lead, 4 operations

create_leadsCreate leadsPOSTCreates leads from an array of lead objects and returns the new identifiers.
get_leadGet leadGETReturns a single lead as a bare object, without the collection envelope.
list_leadsList leadsGETReturns a page of leads under _embedded.leads.
update_leadUpdate leadPATCHApplies a partial update to a single lead and returns its id and new updated_at.

Company, 2 operations

create_companiesCreate companiesPOSTCreates companies from an array of company objects and returns the new identifiers.
list_companiesList companiesGETReturns a page of companies under _embedded.companies.

Note, 2 operations

create_notesCreate notesPOSTCreates notes on leads, contacts, companies or customers and returns the new identifiers.
list_notesList notesGETReturns a page of notes for one kind of record, leads, contacts, companies or customers, under _embedded.notes.

Task, 2 operations

create_tasksCreate tasksPOSTCreates tasks from an array of task objects and returns the new identifiers.
list_tasksList tasksGETReturns a page of tasks under _embedded.tasks.

Custom field, 1 operation

list_custom_fieldsList custom fieldsGETReturns the custom field definitions for leads, contacts, companies or customers under _embedded.custom_fields.

Pipeline, 1 operation

list_pipelinesList pipelinesGETReturns all pipelines under _embedded.pipelines, each with its stages nested inside.

Pipeline status, 1 operation

list_pipeline_statusesList pipeline statusesGETReturns every stage of one pipeline under _embedded.statuses.

Tag, 1 operation

list_tagsList tagsGETReturns the tags available for leads, contacts, companies or customers under _embedded.tags.

User, 1 operation

list_usersList usersGETReturns the account users under _embedded.users, with rights when asked for.

Use Kommo from Claude Code, Cursor or Codex

Connect Kommo in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Kommo operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Kommo

Create your workspace
Sign up free. Nothing to install.
Connect Kommo once
Add your Kommo connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Kommo integration FAQ

What can you do with the Kommo integration?

LiveContext exposes 19 operations on Kommo, covering contact, lead, company and note. Common uses include reporting on open deals per stage, advancing a deal to the next stage and mapping a stage name to a status_id.