@elitedcs/ghl-mcp 3.82.0 → 3.83.1

package/CHANGELOG.md

@@ -1,5 +1,72 @@
 # Changelog
 
+## Unreleased
+
+## 3.83.1 — the Blueprint skill stops asking for the funnel 3.83.0 removed
+
+3.83.0 took funnels out of Blueprint installation, but the installed skill was not
+updated with it. `skills/blueprint/SKILL.md` still listed `funnels` among the arrays
+its plan must carry, and still asked "Build this funnel inside GoHighLevel, or as a
+custom site you host?" with GoHighLevel as the stated default. The skill ships inside
+the package, so anyone running Blueprint produced a plan carrying a key their own
+plan format forbids and their own build step refuses.
+
+The skill and its README now say plainly that Blueprint builds no funnel, page or
+website, and that pages are a separate job after the account exists, on hosting the
+member owns. A test pins the skill and the plan format together so they cannot
+disagree again.
+
+
+## 3.83.0 — a build you can check, and no funnel at the end of it
+
+**Blueprint no longer builds a funnel, a page, or a website of any kind.** GoHighLevel's own page
+builder was never good enough to hand a client, so Build stopped pretending. A build plan that asks
+for one is refused rather than half-built: the plan format forbids it and the executor stops with
+"GHL Command no longer includes funnels of any kind in Blueprint installation." Pages and funnels
+become their own job after the account exists, on hosting the member owns.
+
+**Verify now reads the account back and tells you what it found.** Every object the plan asked for is
+looked up in the sub-account and reported as there or missing, one line each. "Not checked" is treated
+as a defect, not a pass. Verify submits one test lead through the real form and deletes it again, and
+it says so on screen before it does. Verify can no longer claim anything its own read-back contradicts.
+"Verify passed" means the build did its job; the drafts and your own jobs are the next step's work.
+
+**The report is written to be read.** The Verify page was 46 pages long if you printed it; it is now 8,
+with a short findings list instead of sixty near-identical lines, and the duplicate "still to do" list
+is gone. The client handoff is no longer one run-on sentence.
+
+**Workflows arrive as drafts on purpose**, so nothing fires at a client before a person has read it.
+
+Also in this release: staff that GoHighLevel will not let the API create are shown as your job rather
+than reported as a failure; a create that cannot be confirmed is reported honestly instead of being
+retried into a duplicate; and read-backs retry a timeout but never retry a genuine refusal.
+
+**Members do not need an Anthropic key to run builds.** If you are signed in to Claude on the computer
+running GHL Command, the stages use the plan you already pay for. Saving a key switches every stage to
+usage billing, which the cockpit and the member hub now say plainly.
+
+
+- Brief checks the intake and writes the review; the build plan is prepared when Build runs.
+- Changed intake answers require a fresh review, changed build plans require verification, and live workflow repairs need approval of the listed changes.
+- Client pages keep the selected client, open the shared intake answers, separate existing inventory from build evidence, and keep generated drafts for review.
+- Verify prepares the client handoff. Local files are shown as prepared, not published, and handoff email delivery requires a reviewed recipient and explicit confirmation.
+- Your agency now has a creation-only switch for sub-accounts from chat. Package preparation creates catalog products and leaves pricing and payment links as a visible manual task.
+
+
+- Register an existing sub-account on either plan path, replace a saved account key, and see chat registrations in the cockpit without restarting. Creation checks the agency connection first and keeps an account visible when its key could not be saved.
+- Intake keeps Interview answers, loads submitted answers, asks before replacing corrections, and identifies missing respondent details. Source uploads are limited to supported text formats and show the 60,000-character limit. Prepared forms and client documents have clickable links.
+- Client Builds checks account access and setup before running, explains Intake’s writes, and uses the same practice-account rules everywhere. Failed verification blocks sign-off, and manual obligations remain visible until checked.
+- Claude usage records distinguish stages, reviews, rewrites and intake extraction, including calls whose cost was not reported. Questionnaire sending leaves a manual task while the account’s sender cannot be verified.
+
+- You can now save and reopen a client’s intake answers on this computer before its form exists. Form submission and sharing appear once the Intake stage creates the form, with a direct link to the client’s build steps and clear next steps if a request fails.
+
+- The cockpit asks once whether your agency is on Agency Pro and remembers the answer in Your agency. It shows the create form or a masked paste-the-key card, then opens the resulting client’s intake on the same page. A creation refusal or success corrects the saved answer; a read-only company record is retained as evidence, never interpreted as a plan name. The key clears before registration starts and is excluded from confirmations, errors and logs.
+
+- **Sub-account creation requirements clarified.** GHL Command creates sub-accounts on GoHighLevel's Agency Pro plan; on other plans you create it in GoHighLevel and register it in GHL Command with its key. Register each sub-account with its own Private Integration key; registering an agency key does not supply it.
+- **Build a client account guidance corrected.** Existing clients are behind “Work on a client already registered →” and are never pre-selected. Registration confirms the sub-account name and id, never a key hint.
+- **Deletion is separate from registration.** Removing a saved key does not delete the GoHighLevel account. Deletion requires separate authorization; no claim is made that the account's creation method determines whether it can be deleted.
+
+
 ## 3.82.0 — the cockpit laid out like the hub, for Command OS subscribers
 
 The Command OS cockpit was built for one job, the Blueprint build, and that one section

package/LICENSES/Apache-2.0.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/LICENSES/emil-skills-MIT.txt

@@ -0,0 +1,19 @@
+MIT License
+
+Copyright (c) 2026 Emil Kowalski
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/LICENSES/taste-skill-MIT.txt

@@ -0,0 +1,19 @@
+MIT License
+
+Copyright (c) 2026 Leonxlnx
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/NOTICE

@@ -0,0 +1,26 @@
+GHL Command includes Design Studio rules derived from the following works.
+
+Impeccable is by Paul Bakaus and is licensed under Apache License 2.0.
+The relevant design guidance is derived transitively from the frontend-design
+skill by Anthropic, Inc., also licensed under Apache License 2.0.
+The source is https://github.com/pbakaus/impeccable, reached through
+h3nryprod01/design-taste reference/anti-slop.md and reference/interaction-states.md.
+The full licence text is in LICENSES/Apache-2.0.txt.
+
+The taste-skill guidance is by Leonxlnx.
+Copyright (c) 2026 Leonxlnx.
+The source is https://github.com/leonxlnx/taste-skill, reached through
+h3nryprod01/design-taste reference/anti-slop.md and reference/pre-flight.md.
+The copyright and permission notice is in LICENSES/taste-skill-MIT.txt.
+
+The animation guidance is by Emil Kowalski.
+Copyright (c) 2026 Emil Kowalski.
+The source is https://github.com/emilkowalski/skills and specifically
+review-animations/STANDARDS.md.
+The copyright and permission notice is in LICENSES/emil-skills-MIT.txt.
+
+Elite DCs, LLC adapted these facts and thresholds into structured rules,
+measurement instructions and rewrite guidance, and added the house rules.
+The phase 0 port preserves the source catalogue and its provenance block.
+Third-party licence terms apply to their respective portions. This notice
+does not change the licence for the rest of GHL Command.

package/README.md

@@ -49,7 +49,7 @@ Most GHL integrations give you read access and basic CRUD. This server goes far
 | **Funnel & Page Editor** | Read and edit funnel page content — sections, elements, rows, CSS, tracking codes. Goes beyond the public API's list-only access. |
 | **Form Builder** | Full form CRUD including field management, conditional logic, and auto-responder configuration via internal API. |
 | **Pipeline Builder** | Create, edit, and delete pipelines and stages via internal API. The public API only lists pipelines — this lets Claude build them. |
-| **Template Deployment** | Deploy a complete sub-account setup (tags, custom fields, pipelines, workflows, forms) from a single template. Set up a new client in minutes instead of hours. |
+| **Template Deployment** | Deploy tags, custom fields, pipelines, workflows and forms into a registered sub-account from a template. GHL Command creates sub-accounts on GoHighLevel's Agency Pro plan; on other plans you create it in GoHighLevel and register it in GHL Command with its key. |
 | **Multi-Sub-Account Token Registry** | Register multiple sub-accounts with their own API keys. Switch locations mid-session and the API key swaps automatically — no restart needed. |
 | **Full Account Export & Diff** | Export an entire sub-account to JSON or compare two locations side-by-side. Useful for auditing, migration, and quality control. |
 
@@ -155,7 +155,7 @@ Full step-by-step setup with screenshots: [elitedcs.com/ghl-mcp-setup-guide.html
 
 > **CRITICAL: Sub-Account Level Only**
 >
-> Private Integrations in GHL are **scoped to individual sub-accounts**, NOT to the agency level. You must create a separate Private Integration **inside each sub-account** you want to connect. An API key created in Sub-Account A will return `403 Forbidden` if you try to use it with Sub-Account B's Location ID.
+> For location data, use a Private Integration created inside that sub-account. Agency-level Private Integrations also exist, but this agency key cannot replace a sub-account key for contact reads or mint a location token. You must create a separate Private Integration **inside each sub-account** you want to connect. An API key created in Sub-Account A will return `403 Forbidden` if you try to use it with Sub-Account B's Location ID.
 >
 > **Your API key can only be copied ONCE** — at the moment you create the integration. After you leave that screen, the key is permanently masked and cannot be retrieved. If you lose it, you must delete the integration and create a new one.
 
@@ -509,13 +509,13 @@ Highlights (full guide: [`docs/HEADLESS.md`](docs/HEADLESS.md)):
 
 ### Template Deployer (3 tools)
 
-> Deploy a complete sub-account setup from a pre-built template — tags, custom fields, pipelines, workflows, and forms — in one step. Claude walks the user through a questionnaire, then deploys everything. Includes dry-run mode to preview changes before applying.
+> Deploy tags, custom fields, pipelines, workflows and forms into a registered sub-account from a template. Claude collects the requirements and previews the changes in dry-run mode before applying them. GHL Command creates sub-accounts on GoHighLevel's Agency Pro plan; on other plans you create it in GoHighLevel and register it in GHL Command with its key.
 
 | Tool | What It Does |
 |---|---|
 | `list_templates` | List the setup templates that ship with this install (currently one: Clinic / Med Spa) |
 | `get_template_questionnaire` | Get the questionnaire for a template — present to user conversationally |
-| `deploy_template` | Deploy a complete sub-account setup from a template (tags, fields, pipelines, workflows, forms). Supports dry-run mode. |
+| `deploy_template` | Deploy tags, fields, pipelines, workflows and forms into a registered sub-account. Supports dry-run mode. GHL Command creates sub-accounts on GoHighLevel's Agency Pro plan; on other plans you create it in GoHighLevel and register it in GHL Command with its key. |
 
 ### Setup & Diagnostics (3 tools)
 
@@ -652,7 +652,7 @@ ghl-command-mcp/
 │       ├── account-export.ts      # 2 tools — backup & location comparison
 │       ├── workflow-cloner.ts     # 1 tool  — deep workflow cloning
 │       ├── location-switcher.ts   # 6 tools — multi-location support + token registry
-│       └── template-deployer.ts   # 3 tools — deploy sub-account from template (Zod-validated)
+│       └── template-deployer.ts   # 3 tools — deploy assets into a registered sub-account from a template (Zod-validated)
 ├── templates/
 │   ├── clinic-medspa.json         # Clinic/Med Spa blueprint
 │   └── action-schemas.json        # Mandatory workflow action attribute schemas
@@ -842,7 +842,7 @@ Rules of the road:
 
 Some teams keep certain operations human-only — for example sub-account management or messaging — so that a prompt-injected or misbehaving AI session can never touch them. Two controls exist for exactly that:
 
-**1. Sub-account create/delete is OFF by default.** `create_sub_account` and `delete_sub_account` do not register unless you explicitly opt in:
+**1. The chat tools for sub-account creation and deletion are OFF by default.** GHL Command creates sub-accounts on GoHighLevel's Agency Pro plan; on other plans you create it in GoHighLevel and register it in GHL Command with its key. Creation also needs an agency key with `locations.write`. Deletion requires that permission, explicit confirmation and GoHighLevel authorization; the current evidence does not establish its plan gate. These chat tools do not register unless you explicitly opt in:
 
 ```jsonc
 "env": {
@@ -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.82.0
+**Version:** 3.83.1
 
 ---
 

package/dist/capture-helper.js

@@ -71,7 +71,11 @@ var CredentialsSchema = import_zod.z.object({
    *  agency screen and folded into the environment the run inherits.
    *  NEVER printed, logged or sent back to the page — the screen shows only the
    *  last four characters of what is saved. */
-  anthropic_api_key: import_zod.z.string().optional()
+  anthropic_api_key: import_zod.z.string().optional(),
+  anthropic_key_check: import_zod.z.object({ fingerprint: import_zod.z.string(), at: import_zod.z.string(), ok: import_zod.z.boolean() }).optional(),
+  // Desktop OAuth app configuration. Never returned by calendar tools.
+  google_oauth_client_id: import_zod.z.string().optional(),
+  google_oauth_client_secret: import_zod.z.string().optional()
 });
 function appDataDir() {
   const override = process.env.GHL_MCP_CONFIG_DIR?.trim();