Skip to main content
Glama
clarkstamina-max

Kommo CRM MCP Server

by clarkstamina-max
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Kommo CRM MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • 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

    • MCPHub

      GW19ddd
      A
      license
      Not graded
      quality
      A
      maintenance
      Centralizes management and routing of multiple MCP servers, exposing them to AI clients via HTTP/SSE endpoints with configurable visibility, sharing, and smart routing.
      547 npm
      Apache 2.0

    • N8N MCP Server

      rajtrafficradius
      A
      license
      Not graded
      quality
      D
      maintenance
      Production-ready MCP server that brings N8N workflow automation to both Claude.ai and ChatGPT. Supports multi-tenant OAuth/SSE integration with dynamic N8N instance configuration.
      61 npm
      MIT

    • GHL MCP Server

      northrosetech
      A
      license
      B
      quality
      D
      maintenance
      A comprehensive MCP server that connects AI assistants to GoHighLevel CRM, enabling management of contacts, conversations, calendars, pipelines, payments, and more through 60+ tools.
      64
      27 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

    C2.7/5.0

    Scored across 63 tools

    Disambiguation4/5

    Tools are mostly grouped by entity with distinct actions (list, get, create, update, delete), and overlapping tools like create_lead vs create_complex_lead are sufficiently differentiated by description. A few pairs such as get_catalogs and get_catalog_elements could cause slight hesitation, but overall boundaries are clear.

    Naming Consistency4/5

    The vast majority follow a consistent verb_noun snake_case pattern (get_*, create_*, update_*, delete_*). Minor deviations like add_note, add_users, get_available_clients, and launch_salesbot/stop_salesbot prevent a perfect score but do not create real confusion.

    Tool Count2/5

    63 tools is far beyond the comfortable MCP range and will likely bloat agent context and slow tool selection. The broad Kommo CRM domain justifies many operations, but the surface should be curated or split into smaller focused servers to remain practical.

    Completeness3/5

    The toolset covers a wide range of CRM entities and admin features, but there are notable gaps: no get_contact_by_id or get_company_by_id, and no delete operations for leads, contacts, companies, tasks, or notes. These are workable gaps but not a fully complete lifecycle.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources