@elitedcs/ghl-mcp 3.77.0 → 3.78.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +88 -0
- package/README.md +5 -5
- package/dist/index.js +12524 -11021
- package/guide/guide.html +59 -3
- package/package.json +2 -2
- package/skills/blueprint/README.md +1 -1
- package/skills/blueprint/SKILL.md +2 -2
- package/skills/blueprint/references/approval-view.md +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,93 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 3.78.0 — GoHighLevel's own template library, repainted in your client's colours
|
|
4
|
+
|
|
5
|
+
GoHighLevel ships more than 900 designed funnel templates. You could always install
|
|
6
|
+
one and then spend an afternoon recolouring it by hand. Now it is one call.
|
|
7
|
+
|
|
8
|
+
`find_ghl_template` searches the library. `install_ghl_template` installs the one you
|
|
9
|
+
picked into the sub-account you are switched to, and with a `brandSlug` it repaints the
|
|
10
|
+
whole funnel in that brand's colours and typefaces on the way in.
|
|
11
|
+
|
|
12
|
+
**What "repaint" honestly means.** It reads every page of the template first and works
|
|
13
|
+
out ONE palette for the whole funnel, because per-page guessing gave five pages of the
|
|
14
|
+
same template two different second colours. It then swaps that palette for your client's.
|
|
15
|
+
Some large background bands keep the template's own colour, so the result is your
|
|
16
|
+
client's funnel in your client's colours, not a bespoke design. Every branded page is
|
|
17
|
+
read back and measured before anything is removed, and if a single page fails to land,
|
|
18
|
+
nothing is removed at all.
|
|
19
|
+
|
|
20
|
+
**It is careful about your account, and it does not delete anything unless you ask.** It
|
|
21
|
+
installs one funnel and its pages. It touches no workflow, form, pipeline, custom field or
|
|
22
|
+
calendar. The template's original pages are now KEPT by default, sitting beside the branded
|
|
23
|
+
ones, and only removed if you pass `keepOriginals: false`. That is deliberate: the tool
|
|
24
|
+
works out which funnel it just created by comparing the account before and after, and on a
|
|
25
|
+
busy sub-account, where somebody may be building a funnel in the UI at the same moment,
|
|
26
|
+
that comparison cannot be certain. If two new funnels appear it stops and brands nothing.
|
|
27
|
+
If your account holds so many funnels that it cannot see them all at once, or if a step
|
|
28
|
+
holds a split test, it refuses to remove anything and tells you why. Every result carries
|
|
29
|
+
the one call that undoes the whole thing.
|
|
30
|
+
|
|
31
|
+
Run it on a quiet sub-account when you can, and look at the result before asking it to
|
|
32
|
+
remove the originals.
|
|
33
|
+
|
|
34
|
+
These templates are other people's designs, and they are frequently not accessible. The
|
|
35
|
+
tool says so, and points you at `verify_design` on the installed page before a client
|
|
36
|
+
sees it.
|
|
37
|
+
|
|
38
|
+
**Also in this release**
|
|
39
|
+
|
|
40
|
+
Page Studio no longer serves images that belong to other GoHighLevel accounts.
|
|
41
|
+
|
|
42
|
+
A local security fix in the Command OS cockpit. When you start a design run from the
|
|
43
|
+
brand card, the text you type is passed to the run as data. Before this release a
|
|
44
|
+
value that began with two dashes could be read as an instruction instead, which could
|
|
45
|
+
have moved where the run wrote its files. It is contained structurally now, and the
|
|
46
|
+
build fails if anyone reintroduces the old shape.
|
|
47
|
+
|
|
48
|
+
The Security Controls guide PDF had been promising a switch for 233 tools since around
|
|
49
|
+
v3.56.0, because the PDF had no generator and nothing read it back. It now says 250, it
|
|
50
|
+
is rendered from the HTML beside it, and a test reads the finished PDF and fails on a
|
|
51
|
+
stale number.
|
|
52
|
+
|
|
53
|
+
Counts: 250 tools, 51 modules, free tier 112.
|
|
54
|
+
|
|
55
|
+
## 3.77.1 — the Blueprint can build a client account, and had been saying it could not
|
|
56
|
+
|
|
57
|
+
If you ran the Blueprint, it planned the account, showed you the two checklists, and then
|
|
58
|
+
printed this at the bottom:
|
|
59
|
+
|
|
60
|
+
> _v1 stops here. When you approve, the automatic list is ready for one-shot staging (phase 2)._
|
|
61
|
+
|
|
62
|
+
**That was wrong, and it had been wrong for months.** The Blueprint builds. You approve the
|
|
63
|
+
plan, it dry-runs the automatic list without writing anything, shows you exactly what it
|
|
64
|
+
would create, and on your go it builds: pipelines and stages, custom fields, tags, custom
|
|
65
|
+
values, calendars, forms, funnel structure, templates, and workflows chained and verified,
|
|
66
|
+
each object read back before anything that depends on it is created.
|
|
67
|
+
|
|
68
|
+
The plan-only sentence was true of the first version. The builder was finished afterwards
|
|
69
|
+
and nobody removed the old wording. It was in four files, and those files ship inside the
|
|
70
|
+
package, so it has been on your machine reading the wrong thing to you the whole time.
|
|
71
|
+
|
|
72
|
+
**Two of them were worse than a stale sentence.** One instructed the assistant to tell you
|
|
73
|
+
execution was not available yet, so it was not merely present, it was being read out. And
|
|
74
|
+
the description of `apply_build_plan` itself said `execute = live writes (not yet enabled)`
|
|
75
|
+
three hundred lines above the code that performs those writes, which means an assistant
|
|
76
|
+
reading that description could decline to run a build you had just asked for. Meanwhile the
|
|
77
|
+
same skill file gave the correct build instruction further down, so it contradicted itself
|
|
78
|
+
and the half you saw was the false one.
|
|
79
|
+
|
|
80
|
+
**What has not changed is the gate.** Nothing is built until you say so, the dry run still
|
|
81
|
+
writes nothing, and workflows are still created as drafts unless you ask for them
|
|
82
|
+
published. The old wording carried that promise correctly, which is a large part of why the
|
|
83
|
+
false half went unnoticed. The gate stays; only the claim that building does not exist is
|
|
84
|
+
gone.
|
|
85
|
+
|
|
86
|
+
A test now fails the build on any of the six ways this was phrased, anywhere in the skill or
|
|
87
|
+
in that tool, so it cannot come back quietly.
|
|
88
|
+
|
|
89
|
+
Counts unchanged: 248 tools, 51 modules, free tier 112.
|
|
90
|
+
|
|
3
91
|
## 3.77.0 — the account you aimed at, even when two things run at once
|
|
4
92
|
|
|
5
93
|
`switch_location` used to change your API key first and your location a moment later.
|
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# GHL Command — GoHighLevel MCP Server
|
|
2
2
|
|
|
3
|
-
**Full GoHighLevel API access for Claude.**
|
|
3
|
+
**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.
|
|
4
4
|
|
|
5
5
|
**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).
|
|
6
6
|
|
|
@@ -137,7 +137,7 @@ Run setup_ghl_mcp to activate GHL Command:
|
|
|
137
137
|
ghl_location_id: YOUR_LOCATION_ID
|
|
138
138
|
```
|
|
139
139
|
|
|
140
|
-
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 (
|
|
140
|
+
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).
|
|
141
141
|
|
|
142
142
|
### 4. Try it
|
|
143
143
|
|
|
@@ -523,7 +523,7 @@ Highlights (full guide: [`docs/HEADLESS.md`](docs/HEADLESS.md)):
|
|
|
523
523
|
|---|---|
|
|
524
524
|
| `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. |
|
|
525
525
|
| `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. |
|
|
526
|
-
| `enable_workflow_builder` | Add Firebase credentials to an existing install to unlock
|
|
526
|
+
| `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. |
|
|
527
527
|
|
|
528
528
|
### Other Modules
|
|
529
529
|
|
|
@@ -803,7 +803,7 @@ Source repo is private. Contributors need an invitation from `drjerryrelth`. The
|
|
|
803
803
|
|
|
804
804
|
### Reducing context / token usage
|
|
805
805
|
|
|
806
|
-
Every registered MCP tool's schema is shipped to the model on every message. With
|
|
806
|
+
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`:
|
|
807
807
|
|
|
808
808
|
```jsonc
|
|
809
809
|
// Claude Desktop config — enable whole modules
|
|
@@ -897,7 +897,7 @@ Built by **[Elite DCs, LLC](https://elitedcs.com)** — a digital marketing and
|
|
|
897
897
|
|
|
898
898
|
**Tech stack:** TypeScript, Node.js, esbuild, MCP SDK, Zod, GHL API v2, Firebase Auth
|
|
899
899
|
|
|
900
|
-
**Version:** 3.
|
|
900
|
+
**Version:** 3.78.0
|
|
901
901
|
|
|
902
902
|
---
|
|
903
903
|
|