pit-... token.
/mcp/ browser OAuth connection with the V2 MCP endpoint and pass Authorization: Bearer pit-... plus your target sub-account locationId so rotating web sessions never disconnect the tool.
Fix recurring GoHighLevel MCP disconnections for Claude or ChatGPT in sub-account <YOUR_LOCATION_ID>: 1. In Settings > Private Integrations, create a scoped API v2 token (pit-...) with Contacts, Opportunities, Calendars, Conversations, and Workflows permissions and no delete scopes. 2. Configure the client-specific V2 MCP endpoint with Authorization: Bearer <PIT_TOKEN> and locationId: <YOUR_LOCATION_ID> instead of an expiring browser OAuth session. 3. Run a test contact lookup and tag update and verify the event in Contacts and Automation > Workflow > Execution Logs before removing the legacy connection.
# Verify HighLevel MCP connection health and sub-account token scopes ghl-agency doctor --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.
https://services.leadconnectorhq.com/mcp/ URL via interactive browser login get forced to reauthorize every few days whenever the OAuth session token expires or rotates.pit-...) in Settings > Private Integrations, pair it with the V2 MCP endpoint and explicit locationId in Automation > Workflow Builder (or your MCP client config)| Step | Menu Path in GHL | Action |
|---|---|---|
| Step 1 | Settings > Private Integrations | Click Create New Integration, select only the scopes your assistant needs (Contacts, Opportunities, Calendars, Conversations, and Workflows, leaving destructive delete scopes unchecked), and copy the pit-... token. |
| Step 2 | Automation > Workflow Builder | In Automation > Workflow Builder (and your Claude or ChatGPT MCP server settings), replace the legacy /mcp/ browser OAuth connection with the V2 MCP endpoint and pass Authorization: Bearer pit-... plus your target sub-account locationId so rotating web sessions never disconnect the tool. |
| Step 3 | Automation > Workflow > Execution Logs | Run one test contact search and one test tag update through the new MCP connection to confirm it reads and writes in the right sub-account before removing your old connector. |
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 GHL MCP V2 & Private Integration Setup Kit) and weekly live clinics.