Kommo MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Kommo MCP by usefulapi is answering right now. Last checked 12 min ago. It exposes 14 tools. Last commit 6 Nov 2026.

List leads, contacts, companies and tasks; create and update leads in Kommo.

Uptime history 6 days of history

6 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

259 ms

Response time

average over 24h

Stars

last commit 6 Nov 2026

What changed 11

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 November 2026. No other catalogue keeps this.

7 Nov a tool changed version3 times that day

6 Nov a tool changed version3 times that day

5 Nov a tool changed version2 times that day

3 Nov a tool changed version3 times that day

and 7 more, back to 3 November 2026

Nothing serious here today

Today is the operative word: we check Kommo MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add kommo --transport http https://kommo.usefulapi.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://kommo.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.kommo]
url = "https://kommo.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "kommo": {
      "url": "https://kommo.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "kommo": {
      "type": "http",
      "url": "https://kommo.usefulapi.io/mcp"
    }
  }
}

Available tools 14

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

kommo

kommo_create_lead

Create one lead (deal) in a pipeline stage. Creates a new record on every call: it does not check for duplicates. POST /api/v4/leads.

kommo_get_account

Get the Kommo account: id, subdomain, country, currency and the current user id. Good first call to confirm the connection. GET /api/v4/account.

kommo_get_company

Get one company by id, with optional embedded data (contacts, leads). GET /api/v4/companies/{id}.

kommo_get_contact

Get one contact by id, with optional embedded data (leads, companies). GET /api/v4/contacts/{id}.

kommo_get_lead

Get one lead by id, with optional embedded data (contacts, loss_reason, source). GET /api/v4/leads/{id}.

kommo_list_companies

List companies (organisations) with their names, custom fields and responsible user. One request per call. GET /api/v4/companies.

kommo_list_contacts

List contacts (people) with their names, custom fields (email, phone) and responsible user. One request per call. GET /api/v4/contacts.

kommo_list_custom_fields

List the custom fields of leads, contacts or companies (ids, names, types, enum options). Use it to find field ids before writing values. GET /api/v4/{entity}/custom_fields.

kommo_list_leads

List deals (leads) with price, stage, pipeline, responsible user and timestamps. Filter by text, pipeline, owner or the update window. One request per call. GET /api/v4/leads.

kommo_list_notes

List the notes (comments, calls, status changes) of one lead, contact or company. One request per call. GET /api/v4/{entity}/{id}/notes.

kommo_list_pipelines

List the lead pipelines with their stages (status ids, names, sort order). Use it to find the pipeline_id and status_id values for lead filters and writes. GET /api/v4/leads/pipelines.

kommo_list_tasks

List follow-up tasks, optionally only open ones, for one user or one linked entity. One request per call. GET /api/v4/tasks.

kommo_list_users

List the users of the account with their ids, names, emails and roles. Use it to find responsible_user_id values. GET /api/v4/users.

kommo_update_lead

Change one lead: name, value, pipeline, stage or owner. Only the given fields change. Repeating the same call gives the same result. PATCH /api/v4/leads/{id}.

Endpoints

URL	Transport	State	Latency	Checked
https://kommo.usefulapi.io/mcp	streamable-http	answering	167 ms	12 min ago

Alternatives to Kommo MCP by usefulapi

same job, measured the same way

SuiteDash MCP by usefulapi

by usefulapi

Read and update SuiteDash contacts, companies and projects; create leads and clients.

16 tools answering

Keap MCP by usefulapi

by usefulapi

List and create Keap contacts, companies, tasks, opportunities, orders, tags and campaigns.

18 tools answering

Cogmento MCP by usefulapi

by usefulapi

Read Cogmento CRM contacts, companies, deals, tasks and cases; create records and complete tasks.

26 tools answering

Sellsy MCP by usefulapi

by usefulapi

Search and read Sellsy companies, contacts, opportunities, invoices and tasks; create records.

45 tools answering

Jostle MCP by usefulapi

by usefulapi

Read tasks, comments, users and presets; create and update tasks and post comments in Jostle.

7 tools answering

Nozbe Teams MCP by usefulapi

by usefulapi

Read spaces, projects, tasks and comments; create tasks and comments, update tasks in Nozbe Teams.

16 tools answering

Twenty MCP by usefulapi

by usefulapi

Read people, companies, opportunities, notes and tasks; create and update records in Twenty CRM.

20 tools answering

Teamleader Focus MCP by usefulapi

by usefulapi

Read Teamleader Focus contacts, companies, deals, invoices, projects; create deals, tasks.

38 tools answering

Kommo MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Kommo MCP by usefulapi do?

It exposes 14 tools, read directly from the server on our last check. Among them: kommo_create_lead, kommo_get_account, kommo_get_company, kommo_get_contact, kommo_get_lead, kommo_list_companies and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Kommo MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 259 ms. The bar chart above shows every period we have measured.

How do I connect Kommo MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Kommo MCP by usefulapi need an API key?

No. Kommo MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Kommo MCP by usefulapi?

It answers our handshake in 259 ms on average, which is faster than 55% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Kommo MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at kommo.usefulapi.io, which runs on its operator's own terms.