.mcp.json (or ~/.claude.json), configure ghl-crm-mcp with your sub-account's GHL_LOCATION_ID and a location-scoped Private Integration Token from Settings > Private Integrations.
audit_location or workflows_inspect_graph so the assistant pulls your exact custom field keys, tags, pipeline stage IDs, and calendar IDs.
workflows_create_from_recipe, forms_create, or funnels_update_page to build or update automations mapped to your sub-account's real IDs.
Audit and build workflows in our GoHighLevel sub-account using the ghl-crm MCP server: 1. Inspect existing workflows, custom fields, calendars, and tags in sub-account <YOUR_LOCATION_ID>. 2. Identify any missing tags, unmapped custom fields, or broken workflow triggers. 3. Build or update the target workflow graph directly using our sub-account's exact custom field and calendar IDs.
# 1. Inspect sub-account workflows & custom fields via ghl-tools MCP
{
"tool": "workflows_inspect_graph",
"arguments": {
"location_id": "<YOUR_LOCATION_ID>"
}
}
# 2. Or apply a workflow recipe directly via ghl-crm CLI
ghl-crm workflows apply-recipe --location-id <YOUR_LOCATION_ID> --recipe mctb-45s-guard
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.
services.leadconnectorhq.com/mcp) covers public v2 CRM record CRUD—contacts, opportunities, appointments, and conversations—and tells you whether a workflow exists, but it cannot inspect or edit workflow step graphs, funnel page layouts, form builders, DNS records, or sub-account snapshot drift.ghl-tools MCP suite (ghl-crm-mcp, ghl-agency-mcpghl-onboard-mcp) in .mcp.json. ghl-tools does not get superseded by the official MCP because it targets the builder and agency operations the public v2 API omits: workflow graph inspection and recipe provisioning, funnel and website layout JSON, form and survey builders, DNS/CNAME/BIMI verification, snapshot drift checksghl-crm doctor audits.| Step | Menu Path in GHL | Action |
|---|---|---|
| Step 1 | Settings > Private Integrations | Configure ghl-crm-mcp with your sub-account's GHL_LOCATION_ID and a location-scoped Private Integration Token from Settings > Private Integrations. |
| Step 2 | Claude Code | Run audit_location or workflows_inspect_graph so the assistant pulls your exact custom field keys, tags, pipeline stage IDs, and calendar IDs. |
| Step 3 | Claude Code | Run workflows_create_from_recipe, forms_create, or funnels_update_page to build or update automations mapped to your sub-account's real IDs. |
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 Workflow Architect Pack ($47 — or Free with Trial)) and weekly live clinics.