@elitedcs/ghl-mcp 3.77.1 → 3.78.1

package/CHANGELOG.md

@@ -1,5 +1,89 @@
 # Changelog
 
+## 3.78.1 — the template installer stops guessing which funnel it just made
+
+Yesterday's release shipped `install_ghl_template` with the originals kept by default,
+because the tool worked out which funnel it had created by comparing the account before
+and after, and on a busy sub-account that comparison cannot be certain. Keeping the
+originals was the safe answer to an open question.
+
+The question now has an answer. GoHighLevel's install response names what it created: the
+funnel id and its first page. The tool reads that id and waits for that funnel, so it
+cannot land on one somebody else happened to be building at the same moment.
+
+**It does not simply believe it.** The name only counts when your account agrees the
+funnel is genuinely new, and the tool checks the response against a complete picture of
+the account taken before the install. Two independent confirmations, because that one
+field is what authorises removing anything. If the name and the account ever disagree, the
+name is thrown away, nothing is removed, and the result says so.
+
+With both confirmations in hand the originals go back to being removed once every branded
+page has been read back and measured, which is how the tool was meant to work: one clean
+funnel in your client's colours, not a doubled one you have to tidy. Pass
+`keepOriginals: true` if you would rather see both.
+
+Anything less and the originals stay, whatever you passed: no name in the response, a name
+the account cannot corroborate, or an account with so many funnels that the before picture
+was incomplete.
+
+A split-test step, where one step holds more than one page, still stops any removal. Only
+the first page of such a step is rebuilt, so removing the step would take the variants
+with it.
+
+Counts unchanged: 250 tools, 51 modules, free tier 112.
+
+## 3.78.0 — GoHighLevel's own template library, repainted in your client's colours
+
+GoHighLevel ships more than 900 designed funnel templates. You could always install
+one and then spend an afternoon recolouring it by hand. Now it is one call.
+
+`find_ghl_template` searches the library. `install_ghl_template` installs the one you
+picked into the sub-account you are switched to, and with a `brandSlug` it repaints the
+whole funnel in that brand's colours and typefaces on the way in.
+
+**What "repaint" honestly means.** It reads every page of the template first and works
+out ONE palette for the whole funnel, because per-page guessing gave five pages of the
+same template two different second colours. It then swaps that palette for your client's.
+Some large background bands keep the template's own colour, so the result is your
+client's funnel in your client's colours, not a bespoke design. Every branded page is
+read back and measured before anything is removed, and if a single page fails to land,
+nothing is removed at all.
+
+**It is careful about your account, and it does not delete anything unless you ask.** It
+installs one funnel and its pages. It touches no workflow, form, pipeline, custom field or
+calendar. The template's original pages are now KEPT by default, sitting beside the branded
+ones, and only removed if you pass `keepOriginals: false`. That is deliberate: the tool
+works out which funnel it just created by comparing the account before and after, and on a
+busy sub-account, where somebody may be building a funnel in the UI at the same moment,
+that comparison cannot be certain. If two new funnels appear it stops and brands nothing.
+If your account holds so many funnels that it cannot see them all at once, or if a step
+holds a split test, it refuses to remove anything and tells you why. Every result carries
+the one call that undoes the whole thing.
+
+Run it on a quiet sub-account when you can, and look at the result before asking it to
+remove the originals.
+
+These templates are other people's designs, and they are frequently not accessible. The
+tool says so, and points you at `verify_design` on the installed page before a client
+sees it.
+
+**Also in this release**
+
+Page Studio no longer serves images that belong to other GoHighLevel accounts.
+
+A local security fix in the Command OS cockpit. When you start a design run from the
+brand card, the text you type is passed to the run as data. Before this release a
+value that began with two dashes could be read as an instruction instead, which could
+have moved where the run wrote its files. It is contained structurally now, and the
+build fails if anyone reintroduces the old shape.
+
+The Security Controls guide PDF had been promising a switch for 233 tools since around
+v3.56.0, because the PDF had no generator and nothing read it back. It now says 250, it
+is rendered from the HTML beside it, and a test reads the finished PDF and fails on a
+stale number.
+
+Counts: 250 tools, 51 modules, free tier 112.
+
 ## 3.77.1 — the Blueprint can build a client account, and had been saying it could not
 
 If you ran the Blueprint, it planned the account, showed you the two checklists, and then

package/README.md

@@ -1,6 +1,6 @@
 # GHL Command — GoHighLevel MCP Server
 
-**Full GoHighLevel API access for Claude.** 248 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.
+**Full GoHighLevel API access for Claude.** 250 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).
 
@@ -137,7 +137,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 (248 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 (250 tools total with the optional Workflow Builder Firebase add-on).
 
 ### 4. Try it
 
@@ -523,7 +523,7 @@ Highlights (full guide: [`docs/HEADLESS.md`](docs/HEADLESS.md)):
 |---|---|
 | `get_mcp_version` | Check installed version against the latest published to npm. Confirms an upgrade landed after restarting Claude. Available even before GHL credentials are configured. |
 | `health_check` | Run a full health check: npm registry + version status, GHL API key validity, default location reachability, Firebase auth status, token registry presence. Use when something feels broken. |
-| `enable_workflow_builder` | Add Firebase credentials to an existing install to unlock 53 additional Firebase-gated tools (workflow builder, funnel builder, form builder, pipeline builder, workflow cloner, smart lists, reputation, email campaigns, email templates, memberships, validate_workflow). No need to re-enter license / API key / location ID. Run this any time after the basic setup, on the buyer's schedule. |
+| `enable_workflow_builder` | Add Firebase credentials to an existing install to unlock 55 additional Firebase-gated tools (workflow builder, funnel builder, form builder, pipeline builder, workflow cloner, smart lists, reputation, email campaigns, email templates, memberships, validate_workflow). No need to re-enter license / API key / location ID. Run this any time after the basic setup, on the buyer's schedule. |
 
 ### Other Modules
 
@@ -803,7 +803,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 248 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 250 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
@@ -897,7 +897,7 @@ Built by **[Elite DCs, LLC](https://elitedcs.com)** — a digital marketing and
 
 **Tech stack:** TypeScript, Node.js, esbuild, MCP SDK, Zod, GHL API v2, Firebase Auth
 
-**Version:** 3.77.1
+**Version:** 3.78.1
 
 ---