Let's get you running.
You already have a GHL Command license key. Setup is two milestones: core tools live in about 5 minutes, then the Workflow Builder unlock in about 2 more. This page walks you through both, and ends with your first real build.
Get the core tools live
About 5 minutes. At the end of this, Claude can read and run your GHL account: contacts, pipelines, calendars, invoices, bulk operations.
It's in your welcome email from GHL Command — search your inbox for "GHL Command". Can't find it? Email support@ghlcommand.com (or reply to any email from us) and we'll resend it within the day.
One command does it. Open a terminal (Mac: Terminal app · Windows: press the Windows key, type cmd, press Enter), paste this, press Enter:
npx -y @elitedcs/ghl-mcp cli install
It finds Claude Desktop's settings file, adds GHL Command alongside any tools you already have (nothing gets overwritten), and saves a backup first. When it says done, fully quit Claude — Cmd+Q on Mac; on Windows right-click the Claude icon by the clock and choose Quit — then reopen it.
Using Claude Code in the terminal instead? Run: claude mcp add --scope user -t stdio ghl -- npx -y @elitedcs/ghl-mcp@latest
First, get your GHL API key: inside the sub-account you want Claude working on (not the agency view — the URL should read app.gohighlevel.com/v2/location/…), go to Settings → Integrations → Private Integrations → Create New Integration. On the Scopes step click "Select all" at the top of the dropdown. Click Create, then copy the whole pit- key — it's longer than the visible box, so click into the field and select all of it. GHL shows it only once. Your Location ID is the part of that same URL after /location/.
Then tell Claude: "Run setup_ghl_mcp" with your email, license key, GHL API key, and Location ID. Restart Claude once more when it says setup is complete.
Unlock the Workflow Builder
About 2 minutes, one time. The demo where Claude builds and publishes a complete workflow from one sentence? That's the Workflow Builder. It uses GHL's internal API, so it needs one extra credential capture from your browser. Every member does this step. Don't skip it: it's the feature you bought.
Claude runs the one-click capture. A Chrome window opens on the GHL login page (it will say "controlled by automated test software" — that's the tool).
That's your whole job — the tool reads the credentials itself, validates them, and saves them. Restart Claude one last time. The full builder suite is now live: workflows, funnels, forms, pipelines, and the pre-deploy validator.
No window, or a locked-down machine? Ask Claude to "Run auto_capture_firebase_script" — the console-paste path, with screenshots and the script behind a copy button (type allow pasting if Chrome blocks the paste).
Build something real, right now
Paste this into Claude and watch it do what used to be 45 minutes of clicking:
Build and publish a workflow called "New Lead Welcome" that sends an SMS
"Hi {{contact.first_name}}, thanks for reaching out!", waits 1 day, sends a
follow-up email, then adds the tag "nurtured". Summarize what you built.
Then open GHL → Automation and look at it. Live, published, every step chained. Want to start read-only instead? Ask Claude "audit my workflows" first: two minutes, and it finds the broken pipeline and field IDs GHL never warns you about.
Your next client build is the guarantee. Use GHL Command on one real build in your first 30 days. If it doesn't save you at least 5 hours, one email to support and your first month comes back.
Want the lessons, the prompt library, and Jerry answering GHL questions? Join the free community: skool.com/ghl-command-5986/about. Stuck on anything? support@ghlcommand.com — a real person answers within a business day. Full visual walkthrough: the setup guide.