@elitedcs/ghl-mcp 3.66.2 → 3.68.0

package/CHANGELOG.md

@@ -1,5 +1,103 @@
 # Changelog
 
+## 3.68.0 — the checkup
+
+A subscriber asked the question this release is named after: "I'd love for you to
+check my GHL Command to make sure I am using it all and it's all working. Or tell
+me how to check it? Like a checkup from the neckup."
+
+`health_check` already answered half of that, the install half: is the license
+valid, is the key good, is the account reachable. It never answered either of the
+questions people actually have.
+
+Say "run a checkup" and you get three sections.
+
+**Connection** is the old health check, unchanged, folded in so there is one
+thing to run rather than two.
+
+**What still works** is new, and it is the part that matters. Every capability
+area gets one real read against your account, right now: contacts, pipelines,
+calendars, workflows, funnels, forms, invoices, social, phone, the lot. The whole
+section turns on a distinction nothing else in the product made: a clean read
+returning nothing means the feature works and you own none of these, while a 404
+means GoHighLevel changed something. Those two look identical from the outside
+and mean opposite things, so they are never merged. A permission gap and a rate
+limit each get their own verdict too, because each has a different fix, and a
+rate limit has none.
+
+**What you are not using yet** is worked out from what your account contains, not
+from any record of what you have clicked. Nothing about your usage is collected
+or transmitted, which was true before and stays true. Every line ends with the
+exact sentence to paste back.
+
+It is read-only end to end, it works on the free tier, and it is safe to run on a
+live client account.
+
+Two things the first live runs changed, both worth knowing.
+
+GoHighLevel's `/users/` route answers 401 to a perfectly valid key about one call
+in six. Measured, not guessed: two rejections in twelve back-to-back reads, while
+`/contacts/` was clean twelve out of twelve. A single-shot probe would therefore
+tell a paying customer their API key lacks permission roughly every sixth
+checkup. So no failure is reported until it survives three separate reads. Only
+failures retry, so a healthy account pays nothing for it.
+
+And an expired browser login was briefly reported as "Workflow Builder BROKEN,
+send this to support". It is neither broken nor ours, and it has a sixty-second
+fix. A report that cries wolf gets ignored, so token expiry, rate limits, server
+errors and anything else that says nothing about GoHighLevel now say exactly
+that instead of raising an alarm.
+
+**The other half of this release does not ship to anyone.** `scripts/ghl-drift-canary.mjs`
+runs on a schedule against our own test sub-account, boots the real server the
+way Claude does, calls the same `run_checkup` tool, and compares every capability
+against a committed baseline. Nothing watched GoHighLevel before this. The test
+suite mocks the API, so a route they move breaks a shipped tool with every test
+still green, and the first signal was always a support email. Now a capability
+that worked yesterday and fails today opens an alert issue. It also reports its
+own blind spots, because a probe baselined in a broken state can never alert
+again and a canary that quietly shrinks is worse than none.
+
+New tool: `run_checkup`. 242 tools, 51 modules.
+
+## 3.67.0 — the offboarding kit
+
+Every agency has an onboarding checklist. Almost none have an offboarding one, so
+the day a client leaves turns into a week of hunting for logins, exports, and
+"wait, who owns the pixel?"
+
+Ask Claude to build the offboarding kit for an account and you get the whole exit
+package in one go: every contact as a real export rather than the first hundred,
+an inventory of what the account contains, a map of every person and connected
+account that can still get in, and a handoff document written for whoever picks
+the account up next.
+
+Three things it deliberately will not do.
+
+It will not print your keys. GoHighLevel does not hand key values to any tool,
+including this one, so instead you get a list of every place a key lives and the
+instruction to rotate it. That was the useful half anyway.
+
+It will not guess who owns what. GoHighLevel stores nothing about ownership, so
+the kit asks once and writes the answers into the client's own account as custom
+values, where they outlive this tool and the client can read them without asking
+you. Answer them the day you take the client on and every later run is instant.
+Anything unanswered is listed as unanswered, never assumed.
+
+It will not let a short export look like a complete one. The contact export
+reports its own count and GoHighLevel's index count side by side rather than
+claiming they agree, and if it stopped early the handoff document says INCOMPLETE
+in its own text, not in a field somebody has to notice. A section that could not
+be read says so and why, instead of showing zero.
+
+The account you name is the account you get. Both new tools require the
+sub-account explicitly and reach for that account's own key, and the parts that
+depend on the workflow builder refuse outright when the builder is pointed
+somewhere else. Handing one client's webhooks to another on their way out is the
+one mistake an exit package must not be able to make.
+
+**New: `build_offboarding_kit` and `record_asset_ownership`.** 241 tools.
+
 ## 3.66.2 — an export could describe the wrong client
 
 If you asked for one client's account and the server had been started pointing at

package/README.md

@@ -1,6 +1,6 @@
 # GHL Command — GoHighLevel MCP Server
 
-**Full GoHighLevel API access for Claude.** 239 tools across 50 modules — manage contacts, conversations, pipelines, calendars, funnels, workflows, invoices, custom objects, webhooks, and more. **Includes full workflow builder, funnel/page editor, form builder, pipeline builder, bulk operations, account export, and workflow cloning** — capabilities no other GHL tool offers. **Multi-tenant:** one install can run the workflow builder across multiple clients' GHL accounts.
+**Full GoHighLevel API access for Claude.** 242 tools across 51 modules — manage contacts, conversations, pipelines, calendars, funnels, workflows, invoices, custom objects, webhooks, and more. **Includes full workflow builder, funnel/page editor, form builder, pipeline builder, bulk operations, account export, and workflow cloning** — capabilities no other GHL tool offers. **Multi-tenant:** one install can run the workflow builder across multiple clients' GHL accounts.
 
 **Distributed via npm as [`@elitedcs/ghl-mcp`](https://www.npmjs.com/package/@elitedcs/ghl-mcp).** Buyers install with one config block — no git, no Node.js setup, no terminal commands. Updates flow automatically (`npx @latest` re-resolves on every Claude restart).
 
@@ -8,7 +8,7 @@ Works with **both the Claude Desktop App and Claude Code terminal** — your cho
 
 **License required.** Get it at [ghlcommand.com](https://ghlcommand.com?utm_source=npm&utm_medium=readme) — $97/mo, covering UNLIMITED GoHighLevel sub-accounts on up to 3 machines (never billed per account). **30-day time-back guarantee**: save 5+ hours on one client build or your first month back.
 
-**Try it FREE (read-only tier).** Grab an instant free key at [ghlcommand.com/free](https://ghlcommand.com/free?utm_source=npm&utm_medium=readme) — 111 read-only tools on your own GHL account once the two-step install is finished (the same install as the paid tier — upgrading later is just a license swap): the account-wide workflow audit (`audit_workflows` finds the silently broken references GHL never warns you about), account health, and every read across contacts, pipelines, funnels, and workflows. Write tools stay visible and answer with upgrade info. Buying later with the same email upgrades your key in place — 1 machine on free, 3 when you upgrade.
+**Try it FREE (read-only tier).** Grab an instant free key at [ghlcommand.com/free](https://ghlcommand.com/free?utm_source=npm&utm_medium=readme) — 112 read-only tools on your own GHL account once the two-step install is finished (the same install as the paid tier — upgrading later is just a license swap): the account-wide workflow audit (`audit_workflows` finds the silently broken references GHL never warns you about), account health, and every read across contacts, pipelines, funnels, and workflows. Write tools stay visible and answer with upgrade info. Buying later with the same email upgrades your key in place — 1 machine on free, 3 when you upgrade.
 
 **How this differs from HighLevel's official MCP.** HighLevel ships an official Anthropic MCP that reads and writes your CRM (contacts, conversations, calendars, opportunities, payments, social) over the public API — it's free and it's good; use it for that. What it *cannot* do, because the public API doesn't expose it: **build or edit workflows, build funnels/landing pages, or build forms.** That's exactly what GHL Command does — the programmatic Workflow Builder, funnel/page builder, form builder, deep workflow cloning, the silent-failure `audit_workflows`, and Blueprint (build a whole client account from one intake — ships as a guided skill that **installs itself automatically** with this package; nothing to download), all on GHL's internal APIs. **Official MCP = read/write your CRM. GHL Command = build and fix it.** They stack fine together.
 
@@ -135,7 +135,7 @@ Run setup_ghl_mcp to activate GHL Command:
   ghl_location_id: YOUR_LOCATION_ID
 ```
 
-Approve the tool call. Server validates your license, verifies your GHL credentials, writes them to a per-user config file. **Quit Claude one more time and reopen** — the full core toolset is now unlocked (239 tools total with the optional Workflow Builder Firebase add-on).
+Approve the tool call. Server validates your license, verifies your GHL credentials, writes them to a per-user config file. **Quit Claude one more time and reopen** — the full core toolset is now unlocked (242 tools total with the optional Workflow Builder Firebase add-on).
 
 ### 4. Try it
 
@@ -175,7 +175,7 @@ https://app.gohighlevel.com/v2/location/YOUR_LOCATION_ID/dashboard
 
 ## Enable the Workflow Builder
 
-The builder + cloner + validator tools (workflow builder, funnel builder, form builder, pipeline builder, workflow cloner, validate_workflow) use GHL's internal API and require Firebase credentials. Without them, the other 184 tools work fine — you just won't have workflow/funnel/form/pipeline editing. This is the flagship feature: do this step.
+The builder + cloner + validator tools (workflow builder, funnel builder, form builder, pipeline builder, workflow cloner, validate_workflow) use GHL's internal API and require Firebase credentials. Without them, the other 187 tools work fine — you just won't have workflow/funnel/form/pipeline editing. This is the flagship feature: do this step.
 
 **One-click capture (v3.49.0+, the supported path):**
 
@@ -798,7 +798,7 @@ Source repo is private. Contributors need an invitation from `drjerryrelth`. The
 
 ### Reducing context / token usage
 
-Every registered MCP tool's schema is shipped to the model on every message. With 239 tools that's a meaningful per-message context cost even in chats that never touch GHL. If you only use a slice of GHL Command, restrict the tool surface with `GHL_ENABLED_MODULES` and/or `GHL_ENABLED_TOOLS`:
+Every registered MCP tool's schema is shipped to the model on every message. With 242 tools that's a meaningful per-message context cost even in chats that never touch GHL. If you only use a slice of GHL Command, restrict the tool surface with `GHL_ENABLED_MODULES` and/or `GHL_ENABLED_TOOLS`:
 
 ```jsonc
 // Claude Desktop config — enable whole modules