SkillFoxx

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

  • 0 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • The leads and notes modules can change data in AmoCRM
  • The integration key is stored in your own .env
All reasons and checks
Russian stack

makediff-dev/amo-crm-mcpAuthor:makediff-dev

Install

Services

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/amo-crm-mcp

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The leads and notes modules can change data in AmoCRM
  • The integration key is stored in your own .env

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

What it does

The server uses a modular architecture: a shared base layer (BaseServerContext, BaseModule, BaseController) with amo-tasks, amo-pipelines, amo-leads, amo-users, amo-notes and amo-events modules built on top, each with its own controller, service and schemas. The health module exposes a server-health tool with uptime, memory and server metadata. Logging goes to a file so it does not pollute stdout, which stdio transport requires to stay clean. Configuration is read from .env with zod validation, and the server refuses to start on invalid values. The README documents only the basic server-health and get_active_tasks tools, but the code also registers modules for pipelines, leads, users, notes and events.

Who it is for. For developers who want a clean modular base for their own AmoCRM MCP server and are ready to extend it with their own modules.

Good fit when

  • You want a modular MCP server architecture that is easy to extend with your own domain
  • You need AmoCRM tasks, pipelines, leads, users, notes and events in one server
  • You want strict zod-based configuration validation at startup

Not a fit when

  • You need exact documentation for every tool: the README lags behind the code and does not describe all modules
  • You need a ready npm package: the server is built and run from source

Example request

Show active AmoCRM tasks and the MCP server's own status

MCP

Transport
stdio
Authentication
API key

Environment variables

AMO_BASE_URL required
The base API URL, like https://<subdomain>.amocrm.ru/api/v4/.
AMO_INTEGRATION_ID required, secret
The AmoCRM integration identifier.
AMO_INTEGRATION_SECRET required, secret
The integration secret key.
AMO_INTEGRATION_KEY required, secret
The integration access key.

Limitations

The README documents only server-health and get_active_tasks out of the box, even though src/modules/index.ts registers five more modules: pipelines, leads, users, notes and events. The exact tool list and parameters for those modules must be read from the source, since they are undocumented. There is no ready npm package; the server is built locally with npm run build.

How to disable. Remove the server from your MCP client config and stop the dist/index.js process.

FAQ

Are there tools for leads and pipelines?

Yes in the code, the amo-leads and amo-pipelines modules are registered in src/modules/index.ts, but the README does not document them.

Why do logs go to a file instead of the console?

The stdio protocol needs a clean stdout for JSON messages only, so logs default to a file at LOG_FILE_PATH.

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

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

MCP server for amoCRM and Kommo: deals, contacts, tasks and pipeline reports, stalled deals and managers overdue tasks

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 describes the modular architecture, Node.js 18+ requirements, npm install and run steps, zod-validated environment variables, the src layer structure (lib and core), and the server-health and get_active_tasks tools with their return data.

README badge

Report a problem