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
- 0 ★ on the repository
- Last commit
Broad access
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
- Works in
- Services
Manual install
pip install -r requirements.txt
cp .env.example .envInstalling dependencies before filling in the AmoCRM token.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Can create, update and delete contacts and deals with no extra confirmation
- The long-lived token sits in .env with no rotation
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 numberMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
AMO_SUBDOMAINrequired- The AmoCRM account subdomain.
AMO_ACCESS_TOKENrequired, secret- The integration's long-lived access token.
Limitations
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.
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.
Discussion
No questions or reviews yet.
Related
All amoCRM toolsamoCRM MCP Server on FastMCP
amoCRM MCP Server
A FastMCP-based MCP server with 39 tools across 11 amoCRM domains: leads, contacts, analytics and batch operations, deployed as one Vercel project per account
MCP server for the amoCRM (Kommo) API v4: leads, contacts, companies, tasks, pipelines, unsorted inbox and analytics
A minimal MCP server for amoCRM API v4: read and create leads, contacts and notes, with OAuth2 and long-term tokens
A self-hosted, dependency-free Node.js MCP server with 41 tools for Kommo (amoCRM): leads, pipelines, tasks, a live conversation queue, and salesbot
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 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
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| AmoCRM MCP Server on FastMCP (21 tools) (this card) | no | API key | 0 | |
| AmoCRM MCP Server | no | key is optional | 12 | deals, contacts and notes |
| amoCRM MCP Server | no | OAuth | 2 | API v4, funnels |
| amoCRM MCP Server on FastMCP | no | OAuth | 1 | 39 tools |
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.