A side-by-side look at the Lhremote and Ghl Command Feedback MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Lhremote for marketing work as a local process; choose Ghl Command Feedback for marketing as a local process. You can also run both side by side in one block.
mcpServersfind-app, launch-app, quit-app.GHL_API_KEY, GHL_LOCATION_ID, GHL_LICENSE_KEY.get_mcp_version, setup_ghl_mcp, request_license.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 60/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Paid service | Freemium |
| Required env vars | None listed | GHL_API_KEYGHL_LOCATION_IDGHL_LICENSE_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 19 | 1 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 75 | 5 |
| Full listing | View Lhremote | View Ghl Command Feedback |
find-appDetect running LinkedHelper application instances and their CDP connection details.launch-appLaunch the LinkedHelper application with remote debugging enabled.quit-appQuit the LinkedHelper application.list-accountsList available LinkedHelper accounts. Returns account ID, LinkedIn ID, name, and email for each account. Returns accounts in the currently selected workspace by default (LinkedHelper 2.113.x+); set `includeAllWorkspaces` to enumerate every workspace the current LH user belongs to.list-workspacesList LinkedHelper workspaces the current LH user belongs to. Each workspace includes the user's role and a `selected` flag indicating the currently active workspace. Returns an empty list on LinkedHelper versions that predate workspaces (pre-2.113.x).start-instanceStart a LinkedHelper instance for a LinkedIn account.stop-instanceStop a running LinkedHelper instance.check-statusCheck LinkedHelper connection status, running instances, and database health.campaign-listList existing campaigns with summary statistics.campaign-createCreate a new campaign from YAML or JSON configuration.campaign-getGet detailed campaign information including action chain.campaign-exportExport campaign configuration as YAML or JSON.get_mcp_versionCheck 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_mcpFirst-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_licenseGet 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 only programmatic GHL 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_scriptGet 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_interactiveOne-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.Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"alexey-pelykh-lhremote": {
"command": "npx",
"args": [
"-y",
"lhremote"
]
}
}
}
{
"mcpServers": {
"drjerryrelth-ghl-command-feedback": {
"command": "npx",
"args": [
"-y",
"@elitedcs/ghl-mcp@latest"
],
"env": {
"GHL_API_KEY": "YOUR_GHL_API_KEY_HERE",
"GHL_LOCATION_ID": "YOUR_GHL_LOCATION_ID_HERE",
"GHL_LICENSE_KEY": "YOUR_GHL_LICENSE_KEY_HERE"
}
}
}
}