Skip to main content
Glama
runitsolutions

kommo-mcp

by runitsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to kommo-mcp

No user-submitted related servers found.

    Related Servers

    • kommo-mcp

      RonaldoESantosRevOps
      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

    • 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

    • @kama/mcp-server

      AsemanServer
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that auto-discovers Kama CRM API endpoints from OpenAPI spec and exposes them as tools for AI agents to perform CRM operations via natural language.
      21 npm
      MIT

    • kommo-integration-mcp

      vitorssemilio-afk
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets AI validate and create sales funnels (pipelines, stages, custom fields) in Kommo CRM, supporting multiple client accounts with explicit confirmation before writing.
      -
    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

    C2.6/5.0

    Scored across 152 tools

    Disambiguation2/5

    Many tools overlap heavily: every entity has both update (batch) and update_one variants, causing confusion. Analytics tools (kommo_leads_summary, kommo_pipeline_analytics, kommo_sales_report) and search/list tools (kommo_leads_search vs kommo_leads_list) have unclear boundaries. Several call-related tools (kommo_incoming_leads_add_call vs kommo_calls_add) serve similar purposes.

    Naming Consistency3/5

    Most tools follow a kommo_<entity>_<action> pattern with list/get/create/update/delete, but there are notable deviations like kommo_files_create_session, kommo_files_upload_part, kommo_dashboard_get, and kommo_sales_report. The consistent use of 'update_one' and 'assign_one' as suffixes is predictable, but mixed verbs like 'add' vs 'create' and 'launch'/'stop' for bots break the uniformity.

    Tool Count1/5

    152 tools is an extreme number for any MCP server. While the Kommo API is broad, exposing every endpoint individually creates an unwieldy surface. This far exceeds reasonable scoping, overwhelming agents and requiring significant selection effort.

    Completeness3/5

    The tool set covers a wide range of CRM resources (leads, contacts, companies, pipelines, tasks, notes, tags, files, etc.), but several gaps exist: no tag deletion, no catalog custom field delete, no salesbot update/delete, and no direct lead delete tool. The analytics and search conveniences compensate somewhat, but dead ends remain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources