Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Data access / search
List leads, contacts, companies and tasks; create and update leads in Kommo.
1 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Outdated check
Last connection measurement is over 24 hours old. Current availability is unknown.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 3 | 1 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Kommo MCP by usefulapi
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http kommo-mcp-by-usefulapi https://kommo.usefulapi.io/mcpCapabilities
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.
DiscoveredGet the Kommo account: id, subdomain, country, currency and the current user id. Good first call to confirm the connection. GET /api/v4/account.
DiscoveredGet one company by id, with optional embedded data (contacts, leads). GET /api/v4/companies/{id}.
DiscoveredGet one contact by id, with optional embedded data (leads, companies). GET /api/v4/contacts/{id}.
DiscoveredGet one lead by id, with optional embedded data (contacts, loss_reason, source). GET /api/v4/leads/{id}.
DiscoveredList companies (organisations) with their names, custom fields and responsible user. One request per call. GET /api/v4/companies.
DiscoveredList contacts (people) with their names, custom fields (email, phone) and responsible user. One request per call. GET /api/v4/contacts.
DiscoveredList 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.
DiscoveredList 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.
DiscoveredList the notes (comments, calls, status changes) of one lead, contact or company. One request per call. GET /api/v4/{entity}/{id}/notes.
DiscoveredList 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.
DiscoveredList follow-up tasks, optionally only open ones, for one user or one linked entity. One request per call. GET /api/v4/tasks.
DiscoveredList the users of the account with their ids, names, emails and roles. Use it to find responsible_user_id values. GET /api/v4/users.
DiscoveredChange 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}.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 55 ms | 14 |