GHL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GHL_MCP_MODE | No | MCP server mode. Default is read-only. Set to 'read-write' to enable write operations. | read-only |
| GHL_PIT_TOKEN | Yes | Private Integration Token for GoHighLevel (e.g., 'pit-...'). Required; without it the server exits with code 2. | |
| GHL_LOCATION_ID | Yes | The GoHighLevel sub-account/location ID (e.g., 'loc_...') to which the server is bound. | |
| GHL_MCP_APPROVAL_SECRET | No | Approval secret required before any write will run. Not needed when running in the default read-only mode. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Read-only by default. Mutating tools require an approval token. Every write supports dry_run=true. Call server_governance for the current policy and the list of tools that are not implemented.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_contactA | Fetch one contact by id. Returns allowlisted fields only. |
| rate_limit_statusA | Remaining request budget in the client's local sliding window. No network call. |
| search_contactsA | Search contacts in the bound sub-account. Paginates every cursor and reports complete=false when a limit stopped the walk. Returns allowlisted fields only. |
| server_governanceA | This server's own policy: mode, approval requirement, PII allowlist, and the tools that are deliberately not implemented. |
| upsert_contactA | Create or update a contact, deduplicated on email/phone. Idempotent on replay. Pass dry_run=true to preview the change without writing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.