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
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Can create, update and delete contacts and deals with no extra confirmation
- The long-lived token sits in .env with no rotation
Install
Manual install
pip install -r requirements.txt
cp .env.example .envInstalling dependencies before filling in the AmoCRM token.
This is third-party code. Review the repository files before installing.
What it does
The server, built on the FastMCP library, wraps AmoCRM's REST API v4 into 21 tools: search, get, create, update and delete for contacts and deals, listing and creating tasks with a deadline, completing a task, notes on a contact or deal, pipelines and stages, account users, company search and creation, and adding a tag. All the code lives in a single server.py file on httpx with no separate backend layer. Although the README is framed as selling an archive after payment, working source code is already sitting openly in this public repository.
Who it is for. For people who want a minimal single-file MCP server for core AmoCRM operations with no modular architecture and no separate deployment.
Good fit when
- You want a simple single-file server with no build step and no modular structure
- A long-lived AmoCRM token without an OAuth exchange is enough
- You need contacts, deals, tasks, notes, pipelines and companies in one place
Not a fit when
- You are put off by the README being framed as a paid product even though the code is already public: check the license and status yourself
- You need OAuth with automatic token refresh rather than a long-lived AMO_ACCESS_TOKEN
Example request
Create an AmoCRM deal for 200000 rubles with a contact Ivan Petrov and a phone numberLimitations
The README is written as a paid product landing page with a step for receiving an archive after payment, yet the full server.py code is publicly available right in this same repository, which muddies the project's status. No license is stated. It uses only a long-lived token, with no OAuth refresh. Deleting a contact or a deal needs no extra server-side confirmation.
How to disable. Remove the amocrm server from your MCP client config and delete the .env file with the token.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| AMO_SUBDOMAIN required | The AmoCRM account subdomain. |
| AMO_ACCESS_TOKEN required, secret | The integration's long-lived access token. |
Security check
- Can create, update and delete contacts and deals with no extra confirmation
- The long-lived token sits in .env with no rotation
README in short
The Russian README is framed as selling a ready solution: receiving an archive after payment, installing dependencies, getting a token via the aMoMarket and Keys and access sections, setting up .env, and connecting to Claude Desktop. It gives tables of the 21 tools for contacts, deals, tasks, notes and more.
FAQ
Do I need to pay for this server?
The README is framed as a paid product, but the server.py code is already sitting openly in the public GitHub repo.
Does the server support OAuth with token refresh?
No, it only uses a long-lived AMO_ACCESS_TOKEN from the integration settings.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
Yandex Kit skills for store management
kit-skills
Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex
YouGile MCP by Indalo
YouGile MCP
Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit
Bitrix24 portal MCP server
MCP-сервер портала Битрикс24
Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail