GoHighLevel MCP
Related Servers
Alternatives to GoHighLevel MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that provides tools for managing GoHighLevel (GHL) conversations, tasks, and calendar appointments through AI assistants like Claude.2120 npmMIT
- AlicenseNot gradedqualityCmaintenanceA production-grade MCP server that wraps the GoHighLevel API v2, enabling Claude and other MCP clients to interact with GHL CRM as structured tools for managing contacts, conversations, pipelines, appointments, payments, and more.MIT
- AlicenseBqualityDmaintenanceMCP server for GoHighLevel API v2 that provides 50+ tools for CRM, billing, marketing, and operations workflows, enabling natural language interaction with contacts, opportunities, conversations, and more.501MIT
- FlicenseNot gradedqualityBmaintenanceRemote MCP server for GoHighLevel that enables multi-tenant agency access via OAuth, allowing Claude or ChatGPT to use GHL tools through natural language.-
- AlicenseNot gradedqualityCmaintenanceA self-hosted Model Context Protocol server for GoHighLevel CRM, built for agencies. It enables connecting multiple sub-accounts, selecting tools per client, and issuing unique revocable MCP URLs.20 npmMIT
- AlicenseBqualityDmaintenanceA comprehensive MCP server that connects AI assistants to GoHighLevel CRM, enabling management of contacts, conversations, calendars, pipelines, payments, and more through 60+ tools.6439 npm1MIT
TDQS
Scored across 127 tools
With 127 tools spanning many GHL modules, most tools are clearly separated by resource (contacts, conversations, calendars, opportunities, payments, etc.). However, there is direct overlap between ghl_get_contacts and ghl_search_contacts, and similar list/get pairs (e.g., ghl_get_invoices vs ghl_get_invoice) may confuse agents. Descriptions are detailed and generally disambiguate, but the sheer volume introduces some boundary ambiguity.
All tool names follow a consistent snake_case verb_noun pattern with the ghl_ prefix, using verbs like get, create, update, delete, and upsert. The main inconsistency is the mixed use of 'get' and 'list' for retrieval operations (e.g., ghl_get_contacts vs ghl_list_faqs), and some domain-specific verbs like 'purchase' and 'discover'. Overall, naming is predictable and readable.
127 tools is an extreme mismatch for an MCP server, far exceeding the 50+ threshold. Even for a comprehensive platform like GoHighLevel, this volume overwhelms agents and makes tool selection difficult. A more curated set of 15-30 high-level tools would be far more usable.
The server covers a wide range of GHL features with full CRUD for contacts, opportunities, users, knowledge bases, FAQs, and templates. However, several exposed modules are incomplete: funnels are read-only (get only), forms/surveys have no create/update/delete, media library lacks upload, and social posts have no update. These notable gaps mean agents will hit dead ends for common operations.