SkillFoxx

AmoCRM MCP Server (via REST proxy)

AmoCRM MCP Server

A stdio MCP server with seven AmoCRM lead tools that talks not directly to the API but to a separately deployed FastAPI proxy

  • 2 ★ on the repository
  • Last commit
MCP server

Broad access

Why this level

  • Creates and deletes leads in AmoCRM
  • Stores the client secret and access tokens on a separate backend
All reasons and checks
Russian stack

garrik24/mcp-amocrm-serverAuthor:Garrik24

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

Install

Services

Manual install

pip install -r requirements.txt
cp .env.example .env

Installing the FastAPI backend's dependencies and preparing .env before launch.

Access and checks

How we review

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

  • Creates and deletes leads in AmoCRM
  • Stores the client secret and access tokens on a separate backend

This is third-party code. Review the repository files before installing.

What it does

The project has two parts. app.py runs a FastAPI server that handles AmoCRM OAuth authorization, exchanging the code for tokens, refreshing them, a generic CRM entity endpoint, and receiving webhooks. mcp_server.py is a separate stdio MCP server built on the official mcp library that does not talk to AmoCRM directly, but calls the already-running FastAPI proxy's endpoints at the address from the AMOCRM_SERVER_URL variable. The agent gets seven tools: connection status, lead list, creating a simple or full lead, deleting a lead, leads by date range, and a generic amocrm_request call to any proxy endpoint.

Who it is for. For people willing to deploy a separate AmoCRM REST backend on Railway or Heroku and connect an MCP server to it over stdio.

Good fit when

  • You need a separate REST layer over AmoCRM with webhooks and a generic entity endpoint, not just MCP
  • A two-part architecture works for you: your own backend plus a thin MCP client to it
  • You need basic lead operations: list, create, delete, filter by date

Not a fit when

  • You need an MCP server that talks to the AmoCRM API directly without a separate backend: here a running FastAPI proxy is mandatory
  • You need contacts, companies, tasks or notes: the MCP server's tools cover leads only
  • Clean documentation matters: the README has overlapping security notes and repeated instructions

Example request

Show my AmoCRM leads from the last week through MCP

MCP

Transport
stdio
Authentication
OAuth

Environment variables

AMOCRM_SERVER_URL required
The address of the deployed FastAPI backend that the MCP server calls over HTTP.
AMOCRM_CLIENT_ID required, secret
The AmoCRM integration ID for the app.py backend.
AMOCRM_CLIENT_SECRET required, secret
The AmoCRM integration secret for the app.py backend.

Limitations

The MCP server alone is useless without a separately running, network-reachable app.py FastAPI proxy, which has its own AMOCRM_CLIENT_ID, AMOCRM_CLIENT_SECRET, AMOCRM_SUBDOMAIN and REDIRECT_URI variables. The MCP tool set is limited to leads, with no full contact or company coverage. The README shows signs of a security cleanup (removing hardcoded secrets) and several partly overlapping deployment guides.

How to disable. Remove the amocrm server from your MCP client config and stop or delete the deployed FastAPI backend on Railway, Heroku or Vercel.

FAQ

Can I skip the separate backend?

No, mcp_server.py calls app.py's HTTP endpoints via AMOCRM_SERVER_URL, and without a running backend the tools will not work.

Which AmoCRM entities are covered?

The named tools cover leads only; other entities go through the backend's generic POST /api/entities.

Discussion

No questions or reviews yet.

All amoCRM tools
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

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

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

MCP serverBroad access2
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 pure Node.js MCP server with 29 amoCRM tools and a generic call for any API endpoint, launched via npx straight from GitHub

MCP serverBroad access
Russian stack

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

README in short

The README opens with a critical security changes section (secrets removed from code, environment variable validation added), then covers installing dependencies, an .env with AmoCRM parameters, running via uvicorn, authorization and data endpoints, webhooks, and Railway deployment with a list of project environment variables.

README badge

Report a problem