Skip to main content
Glama
E0DUAR

Kommo CRM MCP Server

by E0DUAR

Related Servers

Alternatives to Kommo CRM MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to autonomously interact with Kommo CRM, providing tools for managing pipelines, leads, contacts, and custom fields via the Kommo API v4.
      27
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to perform CRM operations like creating contacts, managing deals, and updating leads through natural language using the Model Context Protocol.
      4
      -
    • 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.
      7 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI models to interact with Zoho CRM via Model Context Protocol, supporting CRUD operations, COQL queries, search, and deal stage management.
      -
    • A
      license
      C
      quality
      C
      maintenance
      MCP server that exposes the Kommo CRM API v4 (plus Files, Conversations, and analytics helpers) as Model Context Protocol tools, resources, and prompts.
      100
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to interact with Twenty CRM data through natural language, providing tools for managing contacts, companies, opportunities, tasks, and more via the Model Context Protocol.
      202 npm
      MIT

    TDQS

    C2.8/5.0

    Scored across 39 tools

    Disambiguation4/5

    Most tools target distinct entities and actions. There is minor overlap between 'list' and 'search' tools for the same entity (e.g., kommo_list_leads vs kommo_search_lead), but descriptions clarify their different use cases.

    Naming Consistency5/5

    All tools follow the consistent pattern 'kommo_[verb]_[entity]' using snake_case. Minor deviations like 'search_contact_by_email' are predictable and do not harm coherence.

    Tool Count4/5

    With 39 tools, the set is on the higher end but still scoped appropriately for a comprehensive CRM. Each major entity has several operations, and the count feels justified.

    Completeness2/5

    The tool set lacks delete operations for all entities (company, contact, deal, lead, note, task) and is missing create/update operations for pipelines and catalog elements. These are significant gaps for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues