@elitedcs/ghl-mcp 3.66.1 → 3.67.0

package/CHANGELOG.md

@@ -1,5 +1,75 @@
 # Changelog
 
+## 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
+another, part of the report came from the other account. Not an error, not a
+warning: the workflows and funnels of a different business, sitting under the
+name of the one you asked about.
+
+It happened because the export asked two different places for "which account",
+and only one of them listened to the account you named. That is now a single
+answer. If the two ever disagree, the export refuses those sections and tells you
+which account it is actually holding and how to switch, rather than answering for
+the wrong one. Everything else in the report was always correct.
+
+Every section also explains itself when it fails now. They used to all say
+"Error fetching", which told you nothing and hid a real permissions error behind
+what looked like a hiccup.
+
+**New guide: Clone and rebrand a site.** Point Claude at a page you have the
+rights to, and get it rebuilt for your client with their name, colours and
+contact details, plus a review list of everything still belonging to whoever
+owned the original: where the leads and payments still go, other people's
+testimonials, claims that came along with the copy. Proven against a real site
+before it was written.
+
+That guide is deliberately separate from building a page inside GHL. Cloning an
+existing page and composing a new one are different jobs that fail in different
+ways, and one guide covering both served neither.
+
+**Blog guide parked.** Reading a list of blog posts does not work — the address
+it calls does not exist, on any account. Rather than ship a guide that depends on
+it, the blog tools are marked as not guide material until that is fixed.
+
 ## 3.66.1 — the tool count was wrong, and so was the thing that checked it
 
 GHL Command has served 239 tools since v3.60.0. Every place we stated the number

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.** 241 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.
 
 **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).
 
@@ -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 (241 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 186 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 241 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