amoCRM MCP Server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
amoCRM MCP Server
MCP (Model Context Protocol) server for amoCRM integration with ChatGPT and other MCP-compatible AI clients.
Features
Leads -- list, get, create, update
Contacts -- list, get, create
Companies -- list, get, create
Tasks -- list, create
Pipelines -- list pipelines and stages
Users -- list account users
Notes -- add and read notes on any entity
Account -- get account info
Salesbot -- inspect Salesbot configurations
Chats -- inspect talks and chat templates
Custom fields -- inspect lead/contact/company fields
Events -- read CRM audit events
Sources and webhooks -- inspect channels and webhook subscriptions
Calls -- add completed call records to CRM cards (does not initiate calls)
Catalogs and tags -- inspect catalog items and entity tags
Widgets -- inspect installed and available widgets
Amma AI agents -- list, inspect, create, update and delete integration-owned agents when the account and integration have the Amma scope
Related MCP server: KommoMCP
Prerequisites
Python 3.10+
amoCRM account with administrator permission to install the integration
Supabase project and Vercel project configured with server-side secrets
Installation
git clone https://github.com/DocAtWork2026/amocrm-mcp.git
cd amocrm-mcp
pip install -r requirements.txtConfiguration
For local stdio mode, configure SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, and MCP_TOKEN_ENCRYPTION_KEY. For production, set them as sensitive Vercel environment variables. Connect the CRM through /connect; do not use legacy long-lived API tokens.
Claude Desktop Setup
Add this server to claude_desktop_config.json using python and the path to server.py.
Available Tools
All original upstream tools are preserved: get_account_info, get_leads, get_lead, create_lead, update_lead, get_contacts, get_contact, create_contact, get_companies, get_company, create_company, get_tasks, create_task, get_pipelines, get_users, add_note, and get_notes.
Upstream
Based on https://github.com/DocAtWork2026/amocrm-mcp (MIT License). This repository was recreated from the upstream source files. Git commit history was not mirrored by the available GitHub connector.
License
MIT
Vercel deployment
This repository exposes 40 amoCRM tools over MCP Streamable HTTP at:
MCP endpoint:
https://amocrm-mcp-ascan-006.vercel.app/mcpHealth check:
https://amocrm-mcp-ascan-006.vercel.app/health
The server.py ASGI application is used by Vercel's Python runtime. The original stdio entry point remains available for local clients. The MCP server currently exposes 40 tools; all 17 upstream tools remain present.
Vercel environment variables
Required:
SUPABASE_URLSUPABASE_SECRET_KEYorSUPABASE_SERVICE_ROLE_KEYMCP_TOKEN_ENCRYPTION_KEY— 64-character hex AES-256-GCM keyMCP_ADMIN_PASSWORD— owner password for OAuth consent
Optional:
AMOCRM_REDIRECT_URI— defaults to the production callbackMCP_ALLOW_WRITE— defaults tofalse; only set totrueto enable CRM write tools
Supabase and encryption keys are server-only. The health endpoint checks connectivity without returning CRM records or credentials.
Security notes
TLS certificate verification is enabled for all outbound amoCRM and Supabase requests.
Entity types used in note endpoints are allowlisted.
Secrets must be configured as sensitive Vercel environment variables and must never be committed.
Remote OAuth deployment
Production MCP endpoint: https://amocrm-mcp-ascan-006.vercel.app/mcp
amoCRM account connection:
https://amocrm-mcp-ascan-006.vercel.app/connectamoCRM callback:
https://amocrm-mcp-ascan-006.vercel.app/oauth/callbackamoCRM external integration secrets webhook:
https://amocrm-mcp-ascan-006.vercel.app/oauth/secretsMCP OAuth uses Authorization Code + PKCE, Dynamic Client Registration, persistent Supabase state, and bearer-token validation.
Owner consent is protected by the sensitive Vercel variable
MCP_ADMIN_PASSWORD.amoCRM credentials and OAuth tokens are encrypted with AES-256-GCM using
MCP_TOKEN_ENCRYPTION_KEY; MCP bearer tokens are stored as SHA-256 hashes.MCP_ALLOW_WRITEdefaults tofalse. Original write tools remain present, but create/update/note operations are blocked unless the owner deliberately sets this variable totrue.SUPABASE_URLandSUPABASE_SERVICE_ROLE_KEYmust be available to the Vercel production runtime.
Extended CRM coverage and boundaries
The extended toolset covers CRM account data, leads, contacts, companies, tasks, pipelines, pipeline stages, custom fields, tags, catalogs, catalog elements, events, sources, webhooks, widgets, Salesbot, talks, chat templates, call logging, and Amma agent lifecycle management.
Important platform boundaries:
The amoCRM REST Calls API records completed calls against CRM cards. It does not place or answer telephone calls. Actual telephony requires a provider/widget or a separate telephony API integration.
AI voice calls require a voice-agent/telephony provider (for example ElevenLabs plus a supported phone/SIP carrier) and separate credentials, phone-number provisioning, and consent/compliance configuration.
amoCRM Chat API uses its own channel registration, scope IDs, and HMAC signatures. It is separate from the CRM OAuth bearer token; message history and sending require a separately registered chat channel.
The public Amma Agents API manages agents connected to an MCP endpoint. It does not document a general endpoint to submit arbitrary prompts to amoCRM's internal Amma model and fetch its generated answer. The API has account availability and integration-scope requirements, and a maximum of two agents created by one integration and ten per account.
The external-integration OAuth button documents
crmandnotificationsscopes. Amma's separate scope must be granted through the appropriate amoCRM integration setup; adding an undocumented scope to the button is not valid.All CRM write tools remain disabled unless
MCP_ALLOW_WRITE=trueis deliberately enabled. Deleting pipelines, agents, widgets, webhooks or fields can be destructive. Field deletion also removes field values.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Remote MCP for amoCRM and Kommo: leads, contacts, tasks, pipelines, chats, Salesbot. OAuth.
Open-source CRM: Claude, ChatGPT or any MCP client works with records, inbox and company knowledge.
Create contacts, move deals, send proposals and invoices, read your inbox, from Claude or ChatGPT.
A CRM you talk to: leads, deals and a pipeline board inside ChatGPT, Grok and other MCP clients.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables users to interact with AmoCRM via Claude Desktop using natural language, with 17 tools for accessing CRM entities like leads, contacts, and pipelines.1834 PyPI1MIT
- FlicenseNot gradedqualityDmaintenanceAI-powered CRM assistant for Kommo/amoCRM that provides natural language management via Telegram bot and MCP protocol, enabling analytics, entity operations, and CRM setup.8-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with amoCRM, providing access to deals, contacts, companies, notes, tasks, and custom fields via natural language.MIT
- AlicenseAqualityFmaintenanceEnables managing amoCRM data through natural language, including leads, contacts, companies, pipelines, tasks, notes, search, events, and unsorted leads.19124 npmMIT