AmoCRM MCP Server
A minimal MCP server for amoCRM API v4: read and create leads, contacts and notes, with OAuth2 and long-term tokens
- 12 ★ on the repository
- Last commit
Broad access
Why this level
- Creates leads, contacts and notes in a production CRM
- Holds amoCRM account access tokens
- HTTP mode without MCP_AUTH_TOKEN exposes the CRM to anyone who reaches the port
Install
- Works in
- Services
Manual install
npm install
npm run buildRun inside the cloned repository; Node.js 18.17 or newer is required.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Creates leads, contacts and notes in a production CRM
- Holds amoCRM account access tokens
- HTTP mode without MCP_AUTH_TOKEN exposes the CRM to anyone who reaches the port
This is third-party code. Review the repository files before installing.
What it does
The server gives the agent a small set of amoCRM actions: paginated lead and contact lists, getting a contact by ID, creating leads and contacts, including in batches, and adding notes to leads, contacts and companies. Auth uses a long-term token or OAuth2; a separate tool exchanges the code for tokens and the access token then refreshes automatically. Besides stdio it serves HTTP and Streamable HTTP protected by a bearer token, and the repo includes a Dockerfile and DigitalOcean deploy scripts.
Who it is for. For integration developers and sales teams who want to create amoCRM leads and contacts from an agent.
Good fit when
- You need to quickly create a lead and contact after a call
- You need to add a note to a lead without opening the UI
- You need a starting point for your own amoCRM MCP server
Not a fit when
- You need pipelines, tasks, search or editing existing leads
- You need a server installable with one npm command
Example request
Create an amoCRM lead named Equipment supply for 250,000 rubles and add a note with the call summaryMCP
- Transport
- stdio
- Authentication
- key is optional
Environment variables
AMO_BASE_URLrequired- amoCRM account URL
AMO_LONG_TERM_TOKENsecret- amoCRM long-term token, the recommended option
AMO_CLIENT_ID- Integration client_id for OAuth2
AMO_CLIENT_SECRETsecret- Integration client_secret for OAuth2
MCP_AUTH_TOKENsecret- Bearer token protecting HTTP endpoints
Limitations
The tool set is small: no updating or deleting leads, no tasks or pipelines. The package is not published, so you build from source and point to dist/index.js. Requires an amoCRM integration with client_id and client_secret or a long-term token. The repo has no license.
How to disable. Delete the amocrm block from your MCP client config and disable the integration or token in amoCRM settings.
FAQ
Which auth method is simpler?
An amoCRM long-term token: no exchange or refresh needed. OAuth2 fits if you already have your own integration.
How do I protect HTTP mode?
Set MCP_AUTH_TOKEN so the endpoints accept only requests with that bearer token.
Discussion
No questions or reviews yet.
Related
All amoCRM toolsMCP server for the amoCRM (Kommo) API v4: leads, contacts, companies, tasks, pipelines, unsorted inbox and analytics
amo-crm-mcp: a modular AmoCRM server
amo-crm-mcp
A TypeScript MCP server with a separate module for each AmoCRM entity: tasks, pipelines, leads, users, notes and events
amoCRM MCP with protection against destructive writes
Я Мебель — amoCRM MCP
An amoCRM API v4 connector with two-tier write protection: edits behind a WRITE_ENABLED flag, deletions need a separate flag plus confirm=true
AmoCRM MCP Server on FastMCP (21 tools)
AmoCRM MCP Server
A compact FastMCP-based MCP server with 21 tools for AmoCRM: contacts, deals, tasks, notes, tags and pipelines in a single server.py
A self-hosted, dependency-free Node.js MCP server with 41 tools for Kommo (amoCRM): leads, pipelines, tasks, a live conversation queue, and salesbot
amoCRM sales manager MCP server
amoCRM ROP MCP Server
An MCP server with business tools on top of amoCRM for a sales manager: department overview, stale deals, manager comparison
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| AmoCRM MCP Server (this entry) | no | key is optional | 12 | |
| amoCRM MCP Server | no | OAuth | 2 | API v4, funnels |
| amoCRM MCP Server on FastMCP | no | OAuth | 1 | 39 tools |
| AmoCRM MCP Server on FastMCP (21 tools) | no | API key | 0 | 21 tools |
Alternatives
Tools by other authors for the same tasks.
- amoCRM MCP Server4 Repository stars
- AmoCRM MCP Server (via REST proxy)2 Repository stars
- AmoCRM MCP Server with pip install and an auth wizard1 Repository stars
README in short
The Russian README covers requirements, environment variables for amoCRM and HTTP protection, and launch commands for stdio, HTTP and Streamable HTTP. It gives a Claude Desktop config pointing to the built file and the OAuth2 token flow. Seven tools are listed with call examples, plus testing via MCP Inspector and separate API test scripts. Other root files go deep into deployment and tokens.