Skip to main content
Glama
ilyaberdysh

amocrm-mcp

by ilyaberdysh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to amocrm-mcp

No user-submitted related servers found.

    Related Servers

    • amoCRM MCP

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

    • amocrm-mcp

      edulabtechnic-source
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code to access amoCRM data such as pipelines, deals, contacts, and users via the MCP protocol.
      15 npm
      MIT

    • Pipedrive MCP Server

      osherai
      A
      license
      A
      quality
      D
      maintenance
      Enables LLMs like Claude to interact with Pipedrive CRM data through a standardized interface, providing 22 tools for managing deals, persons, organizations, activities, and more.
      22
      1
      MIT

    • roistat-mcp

      NatrixAi
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Desktop to interact with Roistat analytics, orders, statistics, call tracking, and clients via 16 supported functions.
      1
      -
    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

    B3.1/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct entity or operation (e.g., leads, contacts, pipelines, tasks). Overlaps like count_and_sum_leads vs get_leads are clearly differentiated in descriptions, leaving no ambiguity for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (primarily get_*), with only minor variations like count_and_sum_leads and get_leads_grouped_by_company that still adhere to the same style.

    Tool Count4/5

    With 18 tools, the server is slightly above the typical 3-15 range, but the count is justified by the breadth of CRM entities covered (leads, contacts, companies, pipelines, tasks, etc.). It remains well-scoped and not excessive.

    Completeness2/5

    The tool set provides extensive read and aggregation capabilities but lacks any create, update, or delete operations. Critical mutations are missing, which would cause agent failures when trying to modify records.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources