Skip to main content
Glama
AustinMander

ghl-mcp

by AustinMander
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ghl-mcp

No user-submitted related servers found.

    Related Servers

    • ghl-mcp

      craig248
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for GoHighLevel sub-accounts, enabling management of CRM contacts, pipelines, calendars, invoices, and more via natural language.
      -

    • CashClaw GHL MCP

      centrender
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for GoHighLevel with 82 live-tested tools, enabling CRM operations like contact management, appointments, invoices, and workflows via natural language.
      36 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

    • ghl-mcp-server-v2

      zackscriven
      A
      license
      C
      quality
      C
      maintenance
      A comprehensive MCP server covering the full GoHighLevel API surface with 651 tools, enabling management of contacts, opportunities, calendars, invoices, and more through natural language, with multi-tenant support and read-only safety defaults.
      100
      36 npm
      1
      MIT

    • GoHighLevel MCP Server

      abdul-34
      A
      license
      Not graded
      quality
      C
      maintenance
      A comprehensive MCP server that connects AI systems to GoHighLevel CRM, providing 269+ tools for contact management, messaging, calendar, sales, and automation.
      10 npm
      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

    B3/5.0

    Scored across 50 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear names and descriptions. There is no ambiguity between tools like list_contacts and search_contacts or between various CRUD operations for different entities.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using lowercase and underscores. Verbs like create, get, list, update, delete, search are used uniformly across the set.

    Tool Count2/5

    With 50 tools, the set is overly large, containing many list_* tools that could be consolidated or reduced. The number exceeds the recommended upper bound for a well-scoped server, making it harder for agents to navigate.

    Completeness3/5

    The tool set covers core CRUD for contacts and opportunities, but lacks CRUD completeness for other entities like invoices (only create and list, no get/update/delete) and conversations (no delete). Some notable gaps exist.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources