Skip to main content
Glama
theAIhomegirl

ghl-mcp-server

by theAIhomegirl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to ghl-mcp-server

No user-submitted related servers found.

    Related Servers

    • GoHighLevel MCP Server

      basicmachines-co
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage GoHighLevel CRM data including contacts, conversations, opportunities, calendars, and forms through MCP tools and resources.
      51
      AGPL 3.0

    • GoHighLevel MCP Server

      REALSolutions605
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to directly interact with the entire GoHighLevel CRM via 563+ tools across 44 categories, allowing natural language control for contacts, messaging, opportunities, calendars, and more.
      17 npm
      1
      ISC

    • GoHighLevel MCP Server

      Abrahamshal
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with GoHighLevel CRM through MCP tools, with support for OAuth 2.1 remote deployment and agency multi-sub-account mode.
      -

    • GoHighLevel MCP Server

      acedev97
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to GoHighLevel CRM via MCP, enabling full sub-account automation with 269+ tools for contacts, messaging, sales, marketing, and more.
      17 npm
      ISC

    • ghl-gold

      MaximKonovalovDev
      F
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to operate GoHighLevel agencies through the official v2 API, managing contacts, deals, conversations, appointments, tags, custom fields, workflows, and pipeline reports with bulk operations and fail-closed security.
      12
      -
    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.8/5.0

    Scored across 55 tools

    Disambiguation2/5

    Several tools have unclear boundaries: opportunities_search_opportunity vs opportunities_search_opportunities_advanced, deprecated contacts_get_contacts vs contacts_search_contacts_advanced, and calendars_get_event_notification vs calendars_find_event_notification. The get/search/find verb variation across similar resources creates frequent ambiguity.

    Naming Consistency1/5

    Naming is highly inconsistent: module prefixes are mixed with camelCase (calendars_getallschedules, calendars_getschedulebyid), verbs vary between get/search/fetch/find, and singular/plural forms are inconsistent (opportunity vs opportunities, resource vs resources). There is no predictable overall pattern.

    Tool Count2/5

    At 55 tools, the server is far over the typical well-scoped range. While it covers multiple modules, the count feels bloated, especially since nearly all dedicated tools are read-only GETs and many could be consolidated.

    Completeness3/5

    The dedicated tool set has obvious gaps: there are no create/update/delete tools for contacts, conversations, tasks, notes, or appointments. However, the ghl_call_endpoint meta-tool exposes all 576 API endpoints, so agents can work around the missing operations, though this creates an awkward dependence on a generic escape hatch.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources