Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @aiwerk/mcp-server-ghl

No user-submitted related servers found.

    Related Servers

    • 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.
      20 npm
      MIT

    • DLF Agency MCP Server

      drleadflow
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage GoHighLevel workspaces through natural language, with 508 tools across 18 domains for complete CRM, marketing, and workflow automation.
      Apache 2.0

    • 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.
      20 npm
      MIT

    • GoHighLevel MCP Server

      drausal
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to interact with GoHighLevel's complete API including contacts, opportunities, calendars, workflows, communications, and business management tools. Supports both Bearer token and OAuth2 authentication with automatic token management.
      20 npm
      8
      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/5.0

    Scored across 569 tools

    Disambiguation2/5

    Many tools are cleanly separated by domain prefixes, but there are numerous exact deprecated duplicates (e.g. agent_studio_get_agent_by_id vs _deprecated, saas_api_get_saas_plan vs _deprecated), and cross-module pairs such as locations_create_custom_field/custom_fields_create_custom_field and emails_fetch_campaigns/campaigns_get_campaigns have identical descriptions. This makes misselection likely despite the mostly clear prefixes.

    Naming Consistency4/5

    Tool names overwhelmingly follow a domain_prefix_verb_noun snake_case pattern (calendars_create_calendar, payments_delete_coupon), which is predictable. There are blemishes like the undocumented text2pay verb, deprecated suffixes, and a few mismatched descriptions/names (products_list_invoices says 'List Products'), but the convention is broadly consistent.

    Tool Count1/5

    At 569 tools, this is an extreme count for an MCP server and far exceeds the 50+ threshold. Even though it wraps a broad platform, the surface is too large for an agent to navigate reliably.

    Completeness3/5

    Coverage is extensive across CRM, invoicing, products, ad management, social media, and SaaS, with many full CRUD lifecycles. However, several modules are read-only or one-off (campaigns_get_campaigns, forms_get_forms, surveys_get_surveys, courses_import_courses), creating notable gaps for those domains.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources