Skip to main content
Glama
wdavidce

Kommo MCP Server

by wdavidce

Related Servers

Alternatives to Kommo MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      9 npm
      1
      MIT
    • 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
    • A
      license
      B
      quality
      C
      maintenance
      Self-hosted MCP server that connects AI assistants to Kommo CRM (API v4), enabling real-time CRM actions such as creating/managing leads, tasks, notes, and more through 29 tools.
      29
      1
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Enables comprehensive integration with Kommo CRM through 25 tools for managing leads, contacts, companies, tasks, events, and generating detailed analytics reports. Supports advanced workflow management, pipeline operations, and real-time performance tracking.
      22
      14
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to the Ploomes CRM, exposing 153 tools for CRUD operations on entities, pipeline and field configuration, CPQ proposal models, automations, and webhooks.
      -
    • F
      license
      C
      quality
      C
      maintenance
      Exposes 153 tools to connect AI assistants to the Ploomes CRM, enabling CRUD operations, funnel configuration, CPQ, automations, and webhooks.
      100
      1
      -

    TDQS

    B3.4/5.0

    Scored across 27 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action (e.g., leads, contacts, pipelines, custom fields, tasks, webhooks, WhatsApp, salesbot). Overlapping purposes like search_leads vs get_lead are clearly differentiated by intent (search vs retrieve by ID). No two tools are ambiguous.

    Naming Consistency4/5

    Tool names consistently follow a verb_noun pattern in snake_case (e.g., create_lead_complex, get_pipelines, send_whatsapp_message). Minor inconsistencies exist, such as 'manage_lead_tags' instead of 'add_remove_lead_tags' and 'add_lead_note' vs 'create_task', but the pattern is generally clear and predictable.

    Tool Count4/5

    27 tools is on the higher side for an MCP server, but the comprehensive coverage of a CRM API including leads, contacts, companies, pipelines, custom fields, tasks, webhooks, and special actions (WhatsApp, salesbot, raw API) justifies the count. Slight over-scoping, but each tool serves a distinct purpose.

    Completeness2/5

    The server lacks delete operations for all major entities (leads, contacts, companies, pipelines, tasks, etc.), which is a notable gap in lifecycle coverage. Additionally, there is no list_all_leads or list_all_tasks tool; search tools may compensate but are not equivalent. The raw API request can fill some gaps, but the surface is incomplete for full CRUD.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues