AmoCRM MCP Server
A minimal MCP server for amoCRM API v4: read and create leads, contacts and notes, with OAuth2 and long-term tokens
Install
npm install
npm run buildRun inside the cloned repository; Node.js 18.17 or newer is required.
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 summaryLimitations
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.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| AMO_BASE_URL required | amoCRM account URL |
| AMO_LONG_TERM_TOKEN secret | amoCRM long-term token, the recommended option |
| AMO_CLIENT_ID | Integration client_id for OAuth2 |
| AMO_CLIENT_SECRET secret | Integration client_secret for OAuth2 |
| MCP_AUTH_TOKEN secret | Bearer token protecting HTTP endpoints |
Security check
- 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
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.
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.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
E-Commerce Skills
E-Commerce Skills by Nexscope
A large set of text skills for Amazon, Shopify, eBay, Etsy, TikTok Shop and Walmart sellers: pricing, listings, ads and growth
153 cross-border e-commerce skills via the LinkFox API: Amazon, Ozon, TikTok Shop, 1688, keywords, ads and patents
An MCP server for Bitrix24 CRM contacts and deals via an inbound webhook: search, lists and deal stage changes