Kommo MCP server
Kommo in any MCP client, through Memtro: Kommo does not publish this server. Memtro's Kommo connector reads Kommo through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Kommo (formerly amoCRM) CRM: leads with their sale value, pipeline, stage, responsible user, dates, tags and linked contacts and companies; contacts by name with their primary email and phone; companies by name; pipelines and their stages; tasks with deadlines; and the account's users by name and email. Other custom field values, note text and chats are never read. Can create and update leads (including moving a lead to another stage), create and update contacts and companies, add a note, and create, change or complete a task, each only when asked.
Reads
kommo_leadsKommo leads (deals): name, sale value (price, in the account's currency), pipeline and stage by name, responsible user id, created…kommo_leadOne Kommo lead by id: name, sale value, pipeline and stage, responsible user, dates, tags, and the ids of its linked contacts…kommo_contactsKommo contacts: id, name, primary email and phone, responsible user, created and updated dates, next task date, tags and linked company ids.kommo_companiesKommo companies: id, name, responsible user, created and updated dates, next task date and tags.kommo_pipelinesKommo lead pipelines and their stages, in order: pipeline id, name, whether it is the main one or archived, and each stage's id, name and type.kommo_tasksKommo tasks: text, deadline, whether completed, the lead, contact or company it is on, responsible user and task type id.kommo_usersThe users (staff) of the Kommo account: id, name and email, to put a name to a responsible_user_id or to assign a lead or task.
Acts, when you ask
These change something in Kommo. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
kommo_create_leadCreate a Kommo lead.kommo_update_leadChange a Kommo lead: rename it, set its sale value, move it to another stage (status_id, with pipeline_id when it is in another pipeline)…kommo_create_contactCreate a Kommo contact, with a full name or first and last name, and optionally a work email and phone, a responsible user and tags.kommo_update_contactChange a Kommo contact's name, first or last name, responsible user, or add and remove tags.kommo_create_companyCreate a Kommo company with a name, and optionally a responsible user and tags.kommo_update_companyChange a Kommo company's name or responsible user, or add and remove tags.kommo_add_noteAdd a plain text note to a Kommo lead, contact or company.kommo_create_taskCreate a Kommo task with a deadline, on a lead, contact or company or on its own, for a responsible user (default the token's user).kommo_update_taskChange a Kommo task's text, deadline or responsible user.kommo_complete_taskMark a Kommo task as completed, with the result Kommo requires (a short text saying what was done), which is kept on the task.
Connect it
First connect Kommo on Dashboard → Connections, then add Memtro to your client once. The Kommo tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Kommo connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which leads are in negotiation this week?
- › What is the total value of leads in the main pipeline?
- › Which of my tasks are overdue?
- › Who is responsible for the BigCo lead?
- › Move the Northwind lead to Contract sent
Questions
- Is this an official Kommo MCP server?
- No. It is Memtro's MCP server with Memtro's Kommo connector behind it: the connector reads Kommo through its API with the credentials you connect on Dashboard → Connections, and Kommo publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Kommo?
- Only when you ask, and only what it has been granted: create a lead, optionally in a given pipeline and stage and linked to contacts and a company (stage automations may run); update a lead: rename it, set its value, move it to another stage or pipeline, reassign it, or add and remove tags (stage automations may run); create a contact, optionally with an email and phone; update a contact's name, responsible user or tags; create a company; update a company's name, responsible user or tags; add a note to a lead, contact or company; create a task on a lead, contact or company; change a task's text, deadline or responsible user; complete a task with a result. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.