GHL MCP Server
Related Servers
Alternatives to GHL MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to pull focused GoHighLevel context before talking to a contact, including contact lookup, timeline summaries, pipeline positions, and appointments, with optional guarded writes. It helps agents brief themselves on a person without exposing raw CRM API noise.6 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable AI clients to operate a GoHighLevel account through chat — searching and updating CRM records, working pipelines and conversations, enrolling contacts in existing workflows, preparing appointments and follow-ups, and inspecting account health across hundreds of GHL API operations. Consequential writes are staged behind confirmation gates, and multiple transport modes and tool profiles keep setup safe for beginners and production use alike.ISC
- FlicenseBqualityCmaintenanceEnables 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-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to inspect personal contacts and create reviewed contact changes through PipMCP, with hosted tool discovery, schema validation, governed execution, write opt-in, and per-call approvals.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to safely operate HubSpot CRM contacts, deals, and pipelines via MCP, with caching, idempotency, audit trails, and robust error handling.15MIT
- AlicenseAqualityBmaintenanceEnables governed access to a canonical Customer Graph across CRM and customer-service records, with per-field provenance, propose-only identity merges, field-level masking, records-only reply drafting, tiered policy and kill-switch enforcement, and hash-chained receipts for auditable reads and internal writes.9MIT
TDQS
Scored across 5 tools
The three contact tools (search_contacts, get_contact, upsert_contact) have crisp, non-overlapping boundaries. The two meta tools, server_governance and rate_limit_status, are both 'server self-info' and could be momentarily confused, but their descriptions clearly separate policy from budget.
All names use snake_case, and the contact tools follow a clean verb_noun pattern (search/get/upsert_contact). server_governance and rate_limit_status break the verb_noun pattern as noun phrases, a minor deviation that is still readable.
Five tools is well within a sensible scope for a narrowly bound contact sub-account server. Two of the five are diagnostic/meta rather than domain operations, making the functional surface slightly thin.
Create/update, single fetch, and search are covered, but there is no delete/archive operation and no way to list or filter beyond cursor pagination (e.g. by tag or owner). Agents will hit a dead end if a contact must be removed or bulk-managed.