SkillFoxx

amoCRM sales manager MCP server

amoCRM ROP MCP Server

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

  • 0 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • move_lead, create_task and add_note write to amoCRM, though move_lead checks the status belongs to the pipeline
  • amoCRM OAuth tokens are stored on the server and grant access to the whole department's deals
All reasons and checks
Russian stack

zimuspro156-lab/amocrm-rop-mcpAuthor:zimuspro156-lab

Install

Services

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/amocrm-rop-mcp-server

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.

  • move_lead, create_task and add_note write to amoCRM, though move_lead checks the status belongs to the pipeline
  • amoCRM OAuth tokens are stored on the server and grant access to the whole department's deals

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

What it does

Instead of a raw wrapper over get_leads and patch_lead, the server gives ready business tools for a sales manager: sales_overview builds a department summary for a period, pipeline_summary shows a stage-by-stage snapshot with counts and totals, manager_performance and compare_managers evaluate one manager or compare several without a good-or-bad rating, find_stale_leads finds deals with no activity for N days, find_overdue_tasks and find_leads_without_tasks catch overdue tasks and deals with no next step, lead_history gives a deal's timeline. Only three write tools remain: create_task, add_note and move_lead, and move_lead first checks that the target status actually belongs to the given pipeline. There are no delete tools or arbitrary PATCH at all. The server deploys on your own server as a systemd service with separate auth circuits: OAuth with PKCE for ChatGPT's incoming access, and separate amoCRM OAuth tokens for outgoing API requests.

Who it is for. For amoCRM sales managers who need not raw data but ready management views: who is falling behind, which deals stalled, what is overdue.

Good fit when

  • You need ready business tools like find_stale_leads, not raw amoCRM API calls
  • It matters that ChatGPT has no access to deleting deals or arbitrary writes
  • You are ready to deploy the server on your own Ubuntu VPS with systemd

Not a fit when

  • You need full amoCRM CRUD, not a limited management set of nine read tools and three write tools
  • You are not ready to deploy a systemd service and HTTPS via Cloudflare Tunnel yourself

Example request

Show deals stalled for more than two days and compare the workload of two managers this week

MCP

Transport
http
Authentication
OAuth

Environment variables

AMOCRM_SUBDOMAIN required
amoCRM account subdomain
AMOCRM_CLIENT_ID required
amoCRM private integration ID
AMOCRM_CLIENT_SECRET required, secret
amoCRM private integration secret key
DEFAULT_PIPELINE_ID
Default pipeline for tools when not explicitly given in the call

Limitations

Only three write tools exist, so the server is not meant for full amoCRM administration. Deployment targets an Ubuntu VPS: install.sh creates a system user, a venv and a systemd unit; another OS needs adaptation. amoCRM authorization is only through a private integration's OAuth; it does not support plain API keys.

How to disable. Stop the service with sudo systemctl stop amocrm-rop-mcp and disconnect the connector in ChatGPT.

FAQ

Can the server delete a deal?

No, there is no delete tool or arbitrary PATCH at all, only nine read tools and three safe write tools.

How are ChatGPT's and amoCRM's authorizations separated?

They are two independent circuits: OAuth 2.0 with PKCE for ChatGPT's incoming requests to the server, and separate amoCRM OAuth tokens for the server's outgoing requests to the CRM; they never overlap.

Discussion

No questions or reviews yet.

All amoCRM tools
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 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 amoCRM and Kommo: deals, contacts, tasks and pipeline reports, stalled deals and managers overdue tasks

MCP serverBroad access
Russian stack

A TypeScript MCP server with a separate module for each AmoCRM entity: tasks, pipelines, leads, users, notes and events

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

README in short

The README explains the difference between a raw API wrapper and business tools, gives an architecture diagram with two auth circuits, full read and write tool tables, amoCRM integration setup steps, local Windows setup, VPS deployment via install.sh and systemd, a separate Cloudflare Tunnel script, updates via update.sh that run tests before restarting, and a detailed troubleshooting table with specific error codes.

README badge

Report a problem