Skip to main content
Glama
jayson-svg

BackCrew GoHighLevel MCP Server

by jayson-svg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to BackCrew GoHighLevel MCP Server

No user-submitted related servers found.

    Related Servers

    • GoHighLevel API v2 MCP Server

      kbgphp
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage GoHighLevel sub-account CRM data, including contacts, custom fields, tags, workflows, and calendar configurations through natural language.
      65 npm
      MIT

    • 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.
      9 npm
      1
      ISC

    • ghl-mcp-server

      RichMarin19
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with GoHighLevel's CRM, marketing automation, and business management tools via the API v2, with support for contacts, conversations, calendars, opportunities, payments, and workflows.
      65 npm
      MIT

    • 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

    A3.6/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (search/list/get). Contacts, opportunities, conversations, and calendars are clearly separated, with no overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: search_, get_, list_. The naming is uniform and predictable across all resources.

    Tool Count5/5

    12 tools is a well-scoped count for a read-only CRM data server. Each tool serves a distinct purpose without being overwhelming or too sparse.

    Completeness4/5

    The set covers the main retrieval needs for contacts, opportunities, conversations, and calendars. Minor gaps exist (e.g., no direct search for a contact's opportunities), but agents can work around using filters.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources