SkillFoxx

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

  • 1 ★ on the repository
  • Last commit
  • MIT
MCP server

Broad access

Why this level

  • Grants CRM access through 17 tools, including data changes
  • OAuth tokens are stored locally in a config.json file
All reasons and checks
Russian stack

ilyaberdysh/amocrm-mcpAuthor:ilyaberdysh

A similar tool with a larger community: AmoCRM MCP Server, 12 ★ on the repository

Install

Services

Manual install

pip install amocrm-mcp

Installing the package before running the amocrm-mcp-auth wizard.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Grants CRM access through 17 tools, including data changes
  • OAuth tokens are stored locally in a config.json file

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 rubles

MCP

Transport
stdio
Authentication
OAuth

Limitations

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.

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.

Discussion

No questions or reviews yet.

All amoCRM tools
Russian stack

A minimal MCP server for amoCRM API v4: read and create leads, contacts and notes, with OAuth2 and long-term tokens

MCP serverBroad access12
Russian stack

A compact FastMCP-based MCP server with 21 tools for AmoCRM: contacts, deals, tasks, notes, tags and pipelines in a single server.py

MCP serverBroad access
Russian stack

MCP server for the amoCRM (Kommo) API v4: leads, contacts, companies, tasks, pipelines, unsorted inbox and analytics

MCP serverBroad access2

amoCRM sales manager MCP server

amoCRM ROP MCP Server

Russian stack

An MCP server with business tools on top of amoCRM for a sales manager: department overview, stale deals, manager comparison

MCP serverExtended access
Russian stack

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 serverBroad access1
Russian stack

A small Node.js amoCRM MCP server with a step-by-step Russian guide that needs no terminal: from an amoCRM token to connecting it in Claude Code through Render

MCP serverExtended access

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.

README badge

Report a problem