AmoCRM MCP Server with pip install and an auth wizard
AmoCRM MCP Server
An AmoCRM MCP server with 17 tools, installed via pip install amocrm-mcp, with OAuth set up through an interactive console wizard
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
- Grants CRM access through 17 tools, including data changes
- OAuth tokens are stored locally in a config.json file
Install
Manual install
pip install amocrm-mcpInstalling the package before running the amocrm-mcp-auth wizard.
This is third-party code. Review the repository files before installing.
What it does
The server acts as a proxy between Claude Desktop and AmoCRM's REST API v4: the agent calls one of 17 tools for leads, contacts and other entities in natural language, and the server decides which API calls to make and in what order, returning JSON. There is no AI inside the server itself; all reasoning happens on Claude's side. It installs via pip install amocrm-mcp, and authorization goes through an interactive amocrm-mcp-auth script that asks for the subdomain, client_id, client_secret and the authorization code from the redirect URL, then saves tokens to ~/.amocrm/config.json.
Who it is for. For Claude Desktop users who want the simplest possible package install and a clear interactive AmoCRM authorization wizard.
Good fit when
- You want a one-command pip install with no manual build from source
- You want a step-by-step interactive wizard for getting an OAuth token without reading AmoCRM docs from scratch
- You work specifically with Claude Desktop and talk to the CRM in Russian
Not a fit when
- You need broad entity coverage: 17 tools is fewer than larger servers in this same category
- You need an SSE or HTTP network transport: the README describes only a local subprocess launch
Example request
Show all my open AmoCRM deals worth more than 100 thousand rublesLimitations
The README does not list all 17 tools by name, only the total count and an architecture diagram. Tokens are stored in ~/.amocrm/config.json with no described encryption mechanism. Getting the authorization code requires manually opening a URL, signing in, and copying the code from the redirect address bar.
How to disable. Remove the amocrm server from claude_desktop_config.json and delete the ~/.amocrm/config.json token file.
MCP
- Transport
- stdio
- Authentication
- OAuth
Security check
- Grants CRM access through 17 tools, including data changes
- OAuth tokens are stored locally in a config.json file
README in short
The Russian README diagrams a request flow from Claude Desktop through the MCP server to the AmoCRM API, gives two install methods, pip install and building from source, four setup steps via the interactive auth wizard, a claude_desktop_config.json setup for both install variants, and a reminder to restart Claude Desktop after changes.
FAQ
Does the server run its own AI model?
No, the README states outright that the server is a proxy between Claude and the AmoCRM REST API, with all call logic on Claude's side.
Where are tokens saved after authorization?
In the ~/.amocrm/config.json file after completing the amocrm-mcp-auth wizard.
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