Related Servers

The descriptions are individually thorough and explicitly call out deprecated/legacy variants, but the sheer volume of near-duplicate pairs makes selection genuinely ambiguous: legacy and v3 twins (e.g. ghl_saas_bulk_disable vs ghl_saas_bulk_disable_deprecated, ghl_email_builder_template_* vs ghl_email_template_*), two opportunity search tools, multiple overlapping 'get Facebook pages' tools across ghl_social_* and ghl_ad_fb_*, and transcription get vs download. Even with careful prose, an agent facing 651 tools will struggle to pick the right one.

The ghl_<domain>_<resource>_<action> pattern is largely consistent, with sensible domain prefixes (contact, calendar, ad_fb, voice_ai) and helpful suffixes like _deprecated and _legacy. Minor deviations exist: verb-first names (ghl_social_get_posts, ghl_blog_get_all_authors_by_location), mixed edit/update verbs (ghl_social_edit_post vs ghl_social_update_queue_item), and ghl_marketplace_charge which reads ambiguously as verb or noun, but overall the system is quite disciplined.

651 tools is an extreme mismatch for a single MCP server, far beyond the 25+ threshold. While it reflects the breadth of the full GoHighLevel platform, no agent can sanely navigate this surface in one server — it should be split into domain-focused servers (contacts, calendars, ad publishing, payments, SaaS, etc.) to keep tool selection tractable and context overhead manageable.

The surface provides full CRUD and lifecycle coverage across dozens of domains: contacts, calendars, opportunities, invoices, payments, products, emails, social posting, ad publishing, voice/conversation AI, knowledge bases, SaaS, and more. The few known gaps (e.g. ghl_user_delete/update missing a path param, form file upload with no callable schema) are documented tool bugs rather than missing operations; there are no obvious dead ends in the core workflows.