GHL MCP Server
Related Servers
Alternatives to GHL MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA comprehensive MCP server that connects AI systems to GoHighLevel CRM, providing 269+ tools for contact management, messaging, calendar, sales, and automation.10MIT
- 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
- AlicenseNot gradedqualityCmaintenanceAn MCP server for GoHighLevel with 82 live-tested tools, enabling CRM operations like contact management, appointments, invoices, and workflows via natural language.21MIT
- AlicenseCqualityCmaintenanceA 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.100211MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for GoHighLevel sub-accounts, enabling management of CRM contacts, pipelines, calendars, invoices, and more via natural language.-
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to GoHighLevel CRM via MCP, enabling full sub-account automation with 269+ tools for contacts, messaging, sales, marketing, and more.11ISC
TDQS
Scored across 64 tools
Most tools follow a clear resource+action pattern making them easy to distinguish, and the ghl_ prefix groups them coherently. The main overlap is ghl_update_opportunity and ghl_update_opportunity_status, since update_opportunity already claims to handle status changes, and the many list_* tools for similar marketing resources (forms, surveys, funnels, blogs) require careful attention.
Every tool uses the ghl_ prefix with a consistent snake_case verb_noun pattern (list, get, create, update, delete, search, send, add, remove). Verbs are used predictably across resource types, with no mixed casing or stylistic deviations.
64 tools is far beyond the range an agent can efficiently navigate, despite the breadth of the GoHighLevel domain. While each tool targets a distinct resource, the sheer size creates significant tool-selection overhead and makes the server unwieldy compared to well-scoped alternatives.
Core lifecycles are well covered: contacts have full CRUD plus tags/notes/tasks/workflow operations, opportunities have complete CRUD plus status updates, and invoices cover list/get/create/send/void. Minor gaps exist such as no delete for contact tasks, no update for contact notes, and list-only access to funnels/blogs/links/products, but agents can work around these.