pit-...) limited to the exact objects your MCP server needs (such as Contacts, Opportunities, and Custom Fields) with delete permissions left unchecked, and expose at most 10 focused tools per workspace so tool schemas do not crowd the model context.
{{contact.phone}} and existing pipeline keys instead of inventing duplicate field names.
{{contact.id}}_{{workflow.id}}) on every outbound webhook or MCP write step and check Execution Logs to confirm retry attempts update the existing record rather than creating duplicates.
Configure a schema-locked MCP integration and webhook write flow for sub-account <YOUR_LOCATION_ID>: 1. In Settings > Private Integrations, provision a least-privilege token scoped to Contacts, Opportunities, and Custom Fields without delete permissions. 2. In Settings > Custom Fields, fetch all existing field keys and picklist options first so extraction and classification tasks output exact matching keys. 3. In Automation > Workflow Builder, attach a contact+workflow request key to every write payload so retries update existing records.
# Inspect existing sub-account custom field keys and workflows before creating MCP schemas ghl-crm custom-fields list --context <YOUR_CONTEXT> --location <YOUR_LOCATION_ID> ghl-crm workflows list --context <YOUR_CONTEXT> --location <YOUR_LOCATION_ID>
Official GHL MCP vs. ghl-tools: HighLevel’s official hosted MCP (services.leadconnectorhq.com/mcp) covers public v2 CRM records (contacts, opportunities, appointments, conversations). ghl-tools MCP complements it with workflow graph inspection & recipes, funnel/form builders, DNS/BIMI checks, and ghl-crm doctor audits.
customer_phone, the next names it phone_numberphone, breaking downstream n8n nodes and GoHighLevel field mappings.10 well-described tools per workspace, query Settings > Custom Fields first so proposed schemas reuse existing field keys| Step | Menu Path in GHL | Action |
|---|---|---|
| Step 1 | Settings > Private Integrations | Create a scoped Location token (pit-...) limited to the exact objects your MCP server needs (such as Contacts, Opportunities, and Custom Fields) with delete permissions left unchecked, and expose at most 10 focused tools per workspace so tool schemas do not crowd the model context. |
| Step 2 | Settings > Custom Fields | Require your MCP server to query the sub-account's existing field keys and picklist values before generating or running any extraction task so new workflows map to {{contact.phone}} and existing pipeline keys instead of inventing duplicate field names. |
| Step 3 | Automation > Workflow Builder | Pass a unique request key (such as {{contact.id}}_{{workflow.id}}) on every outbound webhook or MCP write step and check Execution Logs to confirm retry attempts update the existing record rather than creating duplicates. |
Connect Claude Code, Cursor, or OpenAI Codex to our ghl-tools MCP Server & Rust CLI to build workflows, forms, and funnels from your editor, or start your GoHighLevel plan through our partner link to unlock $612+ in ready-to-import kits (including GoHighLevel MCP Server & Schema Toolkit) and weekly live clinics.