Name: Kommo MCP by usefulapi
Author: usefulapi

Kommo MCP by usefulapi

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

Tool-list grade A Remote · Streamable HTTP No auth needed 14 tools v1.1.3 MIT

No reviews yet by usefulapiGitHub The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

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

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http kommo-mcp-by-usefulapi https://kommo.usefulapi.io/mcp

# 2 — ask your agent for something these tools do
#   kommo_get_account, kommo_list_pipelines, kommo_list_users and 11 more

Kommo MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

usefulapi578 servers

25 categories

All 578 servers

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

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

Parameter	Type	Required	Notes
with	string	no	Comma-separated extra data to embed, e.g. 'contacts,loss_reason' (see the Kommo reference for each entity).

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.

No parameter schema on file.

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.

Parameter	Type	Required	Notes
with	string	no	Comma-separated extra data to embed, e.g. 'contacts,loss_reason' (see the Kommo reference for each entity).
page	integer	no	Page number (default 1). Use _links.next in the result to see whether another page exists.
limit	integer	no	Entities per page (max 250; default 50).

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.

Parameter	Type	Required	Notes
entity	string	yes	Entity type: leads, contacts or companies.
page	integer	no	Page number (default 1). Use _links.next in the result to see whether another page exists.
limit	integer	no	Entities per page (max 250; default 50).

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.

Parameter	Type	Required	Notes
query	string	no	Search text across the filled lead fields.
pipeline_id	integer	no	Only leads in this pipeline.
responsible_user_id	integer	no	Only leads owned by this user id.
updated_from	integer	no	Only leads updated at or after this Unix time.
updated_to	integer	no	Only leads updated at or before this Unix time.
order_updated_at	string	no	Sort direction.
with	string	no	Comma-separated extra data to embed, e.g. 'contacts,loss_reason' (see the Kommo reference for each entity).
page	integer	no	Page number (default 1). Use _links.next in the result to see whether another page exists.
limit	integer	no	Entities per page (max 250; default 50).

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

Parameter	Type	Required	Notes
lead_id	integer	yes	Numeric Kommo id.
with	string	no	Comma-separated extra data to embed, e.g. 'contacts,loss_reason' (see the Kommo reference for each entity).

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

Parameter	Type	Required	Notes
query	string	no	Search text, e.g. a name, email or phone.
responsible_user_id	integer	no	Only contacts owned by this user id.
with	string	no	Comma-separated extra data to embed, e.g. 'contacts,loss_reason' (see the Kommo reference for each entity).
page	integer	no	Page number (default 1). Use _links.next in the result to see whether another page exists.
limit	integer	no	Entities per page (max 250; default 50).

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

Parameter	Type	Required	Notes
contact_id	integer	yes	Numeric Kommo id.
with	string	no	Comma-separated extra data to embed, e.g. 'contacts,loss_reason' (see the Kommo reference for each entity).

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

Parameter	Type	Required	Notes
query	string	no	Search text, e.g. a company name.
responsible_user_id	integer	no	Only companies owned by this user id.
with	string	no	Comma-separated extra data to embed, e.g. 'contacts,loss_reason' (see the Kommo reference for each entity).
page	integer	no	Page number (default 1). Use _links.next in the result to see whether another page exists.
limit	integer	no	Entities per page (max 250; default 50).

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

Parameter	Type	Required	Notes
company_id	integer	yes	Numeric Kommo id.
with	string	no	Comma-separated extra data to embed, e.g. 'contacts,loss_reason' (see the Kommo reference for each entity).

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

Parameter	Type	Required	Notes
responsible_user_id	integer	no	Only tasks for this user id.
is_completed	boolean	no	true = completed only; false = open only.
entity_type	string	no	Only tasks linked to this entity type.
entity_id	integer	no	Only tasks linked to this entity id (use with entity_type).
page	integer	no	Page number (default 1). Use _links.next in the result to see whether another page exists.
limit	integer	no	Entities per page (max 250; default 50).

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

Parameter	Type	Required	Notes
entity	string	yes	Entity type: leads, contacts or companies.
entity_id	integer	yes	Numeric Kommo id.
page	integer	no	Page number (default 1). Use _links.next in the result to see whether another page exists.
limit	integer	no	Entities per page (max 250; default 50).

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.

Parameter	Type	Required	Notes
name	string	yes	Lead name.
price	number	no	Deal value.
pipeline_id	integer	no	Pipeline id (see kommo_list_pipelines).
status_id	integer	no	Stage id inside the pipeline (see kommo_list_pipelines).
responsible_user_id	integer	no	Owner user id (see kommo_list_users).

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

Parameter	Type	Required	Notes
lead_id	integer	yes	Numeric Kommo id.
name	string	no	New lead name.
price	number	no	New deal value.
pipeline_id	integer	no	Move to this pipeline id.
status_id	integer	no	Move to this stage id (inside the pipeline).
responsible_user_id	integer	no	New owner user id.

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Kommo MCP by usefulapi or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.1.3 · scanned 6 Nov 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score93

Findings0 threat · 0 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digest6b1eed2e60e13ecb60f5502231aa22ccce19479dd5bb9fd46998fc0740a83171

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
kommo_get_account	no tags
kommo_list_pipelines	no tags
kommo_list_users	no tags
kommo_list_custom_fields	no tags
kommo_list_leads	no tags
kommo_get_lead	no tags
kommo_list_contacts	no tags
kommo_get_contact	no tags
kommo_list_companies	no tags
kommo_get_company	no tags
kommo_list_tasks	no tags
kommo_list_notes	no tags
kommo_create_lead	state-write	state-write: declares destructiveHint: true
kommo_update_lead	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest6b1eed2e60e13ecb

Scanned2026-11-06

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.

Where are you running it?

Tool surface

Release history

Kommo MCP by usefulapi

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also