@theyahia/amocrm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMOCRM_DOMAIN | No | Alias for AMOCRM_SUBDOMAIN (backwards compatibility) | |
| AMOCRM_CLIENT_ID | No | OAuth client ID (required for token refresh) | |
| AMOCRM_SUBDOMAIN | No | Your amoCRM subdomain (e.g. 'mycompany' from 'mycompany.amocrm.ru') | |
| AMOCRM_ACCESS_TOKEN | Yes | OAuth access token | |
| AMOCRM_CLIENT_SECRET | No | OAuth client secret (required for token refresh) | |
| AMOCRM_REFRESH_TOKEN | No | OAuth refresh token (enables auto-refresh on 401) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_leadsA | Search and list deals (leads) in amoCRM. Supports filtering by pipeline, statuses, and full-text search. Use 'with' to embed contacts or loss reasons. |
| get_leadA | Get a single lead by ID with full details. Use 'with' to include linked contacts and catalog elements. |
| create_leadA | Create a new lead (deal) in amoCRM. Requires a name. Optionally set price, pipeline, status, responsible user, and custom fields. |
| update_leadA | Update an existing lead — change name, price, status, pipeline, responsible user, or custom fields. Useful for moving deals between stages. |
| list_contactsB | Search and list contacts in amoCRM. Supports full-text search across name, phone, and email. |
| get_contactA | Get a single contact by ID with full details including custom fields (phone, email, etc.). |
| create_contactA | Create a new contact in amoCRM. Use custom_fields_values to set phone, email, and other fields. |
| list_companiesA | Search and list companies in amoCRM. Use 'with' to embed linked leads and contacts. |
| create_companyA | Create a new company in amoCRM. Use custom_fields_values for address, website, etc. |
| list_pipelinesA | List all sales pipelines with their statuses (stages). Essential for understanding the sales funnel structure before creating or filtering leads. |
| list_tasksA | List tasks in amoCRM. Filter by entity (lead/contact/company), completion status, or responsible user. |
| create_taskA | Create a task linked to a lead, contact, or company. Set deadline (complete_till as Unix timestamp) and task type (1=Call, 2=Meeting, 3=Email). |
| complete_taskA | Mark a task as completed and add a result text. The result will appear in the entity's activity feed. |
| list_unsortedA | List incoming unsorted leads (from forms, email parsing, etc.) that need to be accepted or declined. |
| accept_unsortedA | Accept an unsorted lead — moves it into a pipeline as a real lead. Optionally specify target pipeline, status, and responsible user. |
| add_noteA | Add a note to a lead, contact, or company. Supports common notes, incoming/outgoing call logs, and service messages. |
| searchA | Universal search across amoCRM — finds leads, contacts, and companies matching the query. Min 3 characters. |
| list_eventsA | List events (activity log) in amoCRM. Filter by entity type, entity ID, or event type. Shows status changes, calls, notes, and other activities. |
| get_accountA | Get current amoCRM account info — name, plan, users, task types, etc. Use 'with' to include users_groups, task_types, and amojo_id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Each tool maps to a distinct resource and action, such as list_leads vs get_lead vs create_lead, and list_unsorted/accept_unsorted are clearly separate from regular lead tools. No two tools appear to do the same job.
Tool names consistently use lowercase snake_case verb_noun patterns like list_leads, create_contact, complete_task, and accept_unsorted. The bare 'search' is a reasonable exception for a universal action and does not break the overall convention.
At 19 tools, the set falls into the heavy 16-25 range and begins to feel borderline bloated, even though the CRM domain covers many entities. The organization by entity helps, but the count is above the ideal 3-15 sweet spot.
Core lead and task workflows are well covered, but contacts and companies lack update/delete operations, there is no get_company, and unsorted leads can only be accepted, not declined. These are notable lifecycle gaps that agents may need to work around.