@elitedcs/ghl-mcp 3.95.0 → 3.97.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 CHANGED
@@ -1,5 +1,39 @@
1
1
  # Changelog
2
2
 
3
+ ## 3.97.0: Add a chat bot or a voice agent to a client's account any day after the first build
4
+
5
+ **You can now add one thing to a client's account after its first build, and Claude does it with the same protections as the build.** Ask Claude to add a chat bot or a voice agent to a client's account. First Claude shows you a plan for just that one thing: the bot's instructions, the facts it will know, a written test plan, anything still missing, and an approval code. Nothing is built until you approve that exact plan. The code belongs to that plan, that client account and that day, so an old approval cannot build a different plan or build in a different account. The add then runs on its own, so undoing it removes only what it made. Undoing it needs the workflow builder connection, as every undo does. The add goes to the account that is active in Claude: name a different account and nothing is planned or built until you switch to it.
6
+
7
+ **A new chat bot starts in suggest mode.** It drafts replies for a person to send and never answers on its own. The facts it knows come only from what you give it. It does not book by itself, because no calendar is connected to it: when a lead is a fit, it takes their name and best number, and your team confirms a time. The plan says so. If you give it no facts, the plan says it only takes booking details, and to add prices and hours to train it.
8
+
9
+ **If the account already has a knowledge base, chat bot or voice agent with the same name, the add does not build.** The plan says so before you approve, so you can choose another name or undo the earlier add first. If GoHighLevel's list cannot be read in full, the add does not build either, and says why.
10
+
11
+ **A new voice agent has no phone number yet.** It answers no calls until you give it one, and the plan gives you that as a job.
12
+
13
+ **Every missed call now gets an instant text and a pipeline check.** A caller who already has a card is not given a second one. The follow-up text an hour later goes at most once per caller per hour, not once per call.
14
+
15
+ **Before Missed Call Text-Back goes live, Build checks that nothing else already texts missed callers.** It reads the account's other workflows, changing nothing, and names any live one started by a call, so a missed caller is not texted twice. GoHighLevel also has a missed-call text-back of its own for the whole account, which no read can see. The plan always tells you where to find it: Settings, then Phone System, then Voice, then Voicemail & Missed Call TextBack, then Missed Call Text Back. If "Enable Missed call textback" is ticked, untick it, then reopen the page to check it stayed off.
16
+
17
+ **Texts keep their own Reply STOP line.** If the account adds a STOP line of its own to first texts, a lead may see it twice. That is safe. The plan tells you to remove ours only if you are sure the account's own is on.
18
+
19
+ **A list of what Build would do that was made before your latest approval is never offered for confirming.** Build makes a fresh list first and says so. Nothing is written until you confirm it.
20
+
21
+ **A Build you paused is no longer shown as a failure above that list, and the Queue no longer asks you to confirm an out-of-date list.**
22
+
23
+ **Choosing the sending number: a clearer warning.** When GoHighLevel reports a different number than the one you asked for, the answer no longer says the text went out. It tells you to check the delivery result and the conversation before sending again.
24
+
25
+ ## 3.96.0: Choose which of your numbers a text goes out from, and send it exactly once
26
+
27
+ **You can now say which of an account's phone numbers a text goes out from.** Ask Claude to send a text from a specific number, for example "text Jane from +15555550100". GHL Command first checks that the number is one of that account's own lines. If it is not, nothing is sent and the answer lists the account's real numbers. If the check cannot run, nothing is sent either, and the answer says why.
28
+
29
+ **After the text goes out, GHL Command checks which number GoHighLevel reports it used.** The answer says whether it matches the number you asked for. If GoHighLevel used a different number, the answer says so plainly and tells you not to report it as sent from the number you asked for. If GoHighLevel names the sender only by the account's name instead of a number, the answer says the sender could not be confirmed.
30
+
31
+ **A text can be sent exactly once, with no automatic resend.** Normally, if the connection drops, GoHighLevel says it is busy, or GoHighLevel has an error of its own, GHL Command tries again. For a text that is a risk: the first try may already have gone out, and the person gets it twice. Ask for a single attempt and GHL Command never resends. If that one try fails, the answer says which of two things happened:
32
+ - **Not sent.** GoHighLevel refused it, or GHL Command stopped it before it left. Safe to send again.
33
+ - **May have gone out.** The connection dropped, the try timed out, or GoHighLevel had an error of its own, so there is no way to tell whether it went. Check the conversation before sending again.
34
+
35
+ **Nothing changes unless you ask for it.** Texts that use neither option work exactly as before.
36
+
3
37
  ## 3.95.0: The brain checks a message against the lead's record before it goes out
4
38
 
5
39
  **The brain can now check a message against the lead's record before it goes out.** You add one asking step in front of an SMS or email in a workflow. When a lead reaches it, the brain reads that lead's GoHighLevel record (contact, appointments, invoices and recent messages), its own notes on the lead, your business's path and your past rulings, and answers send or hold. If the brain cannot check it, a reminder still goes out and a message asking the lead for something is held for a person.
package/README.md CHANGED
@@ -904,7 +904,7 @@ Built by **[Elite DCs, LLC](https://elitedcs.com)** — a digital marketing and
904
904
 
905
905
  **Tech stack:** TypeScript, Node.js, esbuild, MCP SDK, Zod, GHL API v2, Firebase Auth
906
906
 
907
- **Version:** 3.95.0
907
+ **Version:** 3.97.0
908
908
 
909
909
  ---
910
910