@elitedcs/ghl-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: elitedcs.com
What it contacted
elitedcs.com
Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.
Starting it
npx -y @elitedcs/ghl-mcp@3.97.13
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.
get_mcp_version | Returned a result 0.2 s · 90 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
get_mcp_version
Check the installed version of GHL Command against the latest version published to npm. Use this to confirm an upgrade landed after restarting Claude. Returns installed version, latest version, whether up-to-date, and the one-line restart instruction if not.
setup_ghl_mcp email, license_key, ghl_api_key, ghl_location_id, ghl_company_id, firebase_paste, ghl_user_id, ghl_firebase_api_key, ghl_firebase_refresh_token
First-run setup AND license upgrades for GHL Command. Validates your license and GHL credentials, then writes them to a per-user credentials file; restart Claude once after it completes. UPGRADING an existing install (e.g. free key to paid)? Supply ONLY email + license_key — the GHL credentials and any Workflow Builder unlock already saved on this machine are reused and kept; do not re-enter ghl_api_key or ghl_location_id. No license yet? Paid ($97/mo) at https://ghlcommand.com — or a FREE read-only key, instantly, at https://ghlcommand.com/free.
request_license email, name
Get a GHL Command license. Use this if you installed from npm but don't have a license yet (or setup_ghl_mcp says your license is missing/invalid). GHL Command is $97/mo — every sub-account you manage, 3-machine activation, includes the workflow builder. There's also a FREE read-only tier (account audits + all reads on your own account) — instant key at https://ghlcommand.com/free. Leave your email and we'll send the purchase link + setup help; the tool also returns where to buy right now.
auto_capture_firebase_script
Get the browser-console script that auto-extracts the 3 Firebase fields needed to enable the Workflow Builder. PREFER `capture_firebase_interactive` when Chrome/Edge is installed (one-click, zero pasting); this script is the fallback for locked-down machines and the path for capturing a CLIENT account's Firebase (multi-tenant). Run this, copy the script, paste it into Chrome DevTools Console on a tab logged into GHL, press Enter, and the result lands in your clipboard. Then paste the JSON into setup_ghl_mcp's firebase_paste field (or enable_workflow_builder's).
capture_firebase_interactive
One-click Workflow Builder unlock (EASIEST PATH — try this before auto_capture_firebase_script). Also the unlock for the FREE tier's account auditor (audit_workflows, validate_workflow) — same one-time login. Opens a Chrome window where you just log into GHL; GHL Command captures the Firebase credentials itself and saves them. No DevTools, no pasting. Re-run the same tool if the first call says it's still waiting for your login. After the first successful run, future re-captures (refresh-token rotations) happen silently with no window at all. Falls back cleanly: if no Chrome/Edge is installed, use auto_capture_firebase_script instead.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Files it wrote
/tmp/ .config/ elitedcs-ghl-mcp/ device.json
Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.
Install facts
| License | SEE LICENSE IN LICENSE |
|---|---|
| Needs | node >=20 |
| Source | github.com/drjerryrelth/ghl-command-feedback |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-XdqRclvLRir+bJgP6CKB6dHZN6cmhRsM8pYiDtLla6NIWoOKXh1mmw/xRBB9LjJ8RvkbT9KuEwhKYqTeoGbo9Q== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 3.97.13 | 2026-11-16 | Starts with no setup | 5 |
| 3.97.10 | 2026-11-12 | Starts with no setup | 5 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40elitedcs/ghl-mcp)
New version out? Ask for a fresh report.