Skip to main content
Glama
theYahia

@theyahia/amocrm-mcp

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @theyahia/amocrm-mcp

No user-submitted related servers found.

    Related Servers

    • amoCRM MCP

      ivan000vovanov
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with amoCRM, providing access to deals, contacts, companies, notes, tasks, and custom fields via natural language.
      6 npm
      MIT

    • KommoMCP

      ampulex-23
      F
      license
      Not graded
      quality
      D
      maintenance
      AI-powered CRM assistant for Kommo/amoCRM that provides natural language management via Telegram bot and MCP protocol, enabling analytics, entity operations, and CRM setup.
      7
      -

    • amocrm-mcp

      ilyaberdysh
      A
      license
      B
      quality
      D
      maintenance
      Enables users to interact with AmoCRM via Claude Desktop using natural language, with 17 tools for accessing CRM entities like leads, contacts, and pipelines.
      18
      1
      MIT

    • amoCRM MCP Server

      DocAtWork2026
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for amoCRM integration, enabling AI assistants to manage leads, contacts, companies, tasks, and more via natural language.
      4
      MIT

    • Kommo CRM MCP Server

      E0DUAR
      A
      license
      C
      quality
      D
      maintenance
      Enables AI agents to manage Kommo CRM (formerly AmoCRM) entities including leads, contacts, companies, tasks, notes, pipelines, and products through natural language commands via the Model Context Protocol.
      39
      11 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 19 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources