amoCRM 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
- 1 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Creates and updates leads, contacts and companies
- Stores the OAuth client_secret and refresh_token for auto-refresh
Install
- Works in
- Services
Manual install
pip install -e .
cp .env.example .envInstalling the server from source before filling in .env.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Creates and updates leads, contacts and companies
- Stores the OAuth client_secret and refresh_token for auto-refresh
This is third-party code. Review the repository files before installing.
What it does
The server is built on the FastMCP library and covers amoCRM's API v4 with 39 tools across 11 domains: leads, contacts, companies, tasks, notes, pipelines, associations, account, batch, unsorted and analytics. Tokens refresh automatically with disk persistence, there is a long-lived token mode for simple single-account setups, request rate limiting at 7 per second with 429 backoff, HAL and JSON normalization, and a consistent data-or-error response envelope. It supports stdio, SSE and streamable-http transports. The README describes a production pattern: one Vercel project per amoCRM account, with environment variables in the project settings.
Who it is for. For developers who need a full-featured amoCRM MCP server with a ready Vercel deployment and support for multiple transports.
Good fit when
- You need leads, contacts, companies, tasks, analytics and batch operations in one server
- You need a remote HTTP deployment on Vercel, not just local stdio
- You need built-in rate limiting and automatic OAuth token refresh
Not a fit when
- You need one amoCRM account shared by several clients at once: the README's production pattern is one Vercel project per account
- You do not want a separate Vercel deployment and prefer a purely local server
Example request
Pull analytics on deals in my amoCRM pipeline for this monthMCP
- Transport
- stdio, sse, http
- Authentication
- OAuth
Environment variables
AMO_SUBDOMAINrequired- The amoCRM account subdomain.
AMO_ACCESS_TOKENrequired, secret- A long-lived access token for the simple single-account mode.
AMO_CLIENT_IDsecret- The integration ID for automatic token refresh, together with CLIENT_SECRET and REFRESH_TOKEN.
Limitations
For production the README explicitly describes a one-Vercel-project-per-amoCRM-account pattern, so multiple accounts need multiple deployments. Service health is checked via a separate /healthz endpoint that you need to monitor yourself. It requires your own amoCRM OAuth integration with a client_id, client_secret and refresh_token, or a long-lived token.
How to disable. Remove the amocrm server from your MCP client config and stop or delete the Vercel project if you used the cloud deployment.
FAQ
Can one server serve multiple amoCRM accounts?
The README describes a one-Vercel-project-per-account production pattern, so multiple accounts need multiple deployments.
Which transports are supported?
stdio for local runs, plus SSE and streamable-http via the AMO_TRANSPORT and AMO_PORT variables for network access.
Discussion
No questions or reviews yet.
Related
All amoCRM toolsAmoCRM 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
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
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
A self-hosted, dependency-free Node.js MCP server with 41 tools for Kommo (amoCRM): leads, pipelines, tasks, a live conversation queue, and salesbot
MCP server for amoCRM and Kommo: deals, contacts, tasks and pipeline reports, stalled deals and managers overdue tasks
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 (this card) | no | OAuth | 1 | |
| 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 (21 tools) | no | API key | 0 | 21 tools |
README in short
The README lists 39 tools across 11 domains, features like rate limiting, HAL normalization and three transports, gives a pip install -e . setup, .env configuration with minimal and full variable sets, three transport-based launch methods, a Claude Desktop config, and a Vercel deployment section with project environment variables and /mcp and /healthz endpoints.