Kommo MCP by usefulapi

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.usefulapi/kommo and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 2 Nov 2026. Not supplied by the maker.

• 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_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_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_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_get_lead

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

• 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_get_contact

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