One Unified HighLevel MCP Across Every Agentic IDE
Different editors expect different MCP configuration formats (`serverUrl` in Windsurf, `cline_mcp_settings.json` with `alwaysAllow` in Cline, `context_servers` in Zed). Hand-writing these configs causes connection errors.
Automated Config Generation (`ghl-agency init-config`)
- `ghl-agency init-config --client windsurf` generates `~/.codeium/windsurf/mcp_config.json`.
- `ghl-agency init-config --client cline` generates `cline_mcp_settings.json` with safe read-only bootstrap tools pre-configured.
- `ghl-agency init-config --client zed` generates `~/.config/zed/settings.json` (`context_servers`).
- All three bundles are pre-built and SHA-256 verified under `docs/publishing/generated/{windsurf,cline,zed}`.
Side-by-Side Technical & Pricing Comparison
| Capability / Requirement | Manual Config Editing | Generic Node MCPs | HighLevel Agency & Builder MCP |
|---|---|---|---|
| Exact Schema for Windsurf, Cline & Zed | ⚠️ Trial-and-error JSON keys | ⚠️ Stdio-only Node scripts | ✅ Built-in `init-config --client windsurf|cline|zed` |
| Safe Bootstrap Auto-Approve (`alwaysAllow`) | ❌ Manual per-tool clicking | ⚠️ Unsafe write auto-approval | ✅ Pre-configures safe read-only discovery tools |
CLI & MCP Configuration
# Windsurf (~/.codeium/windsurf/mcp_config.json)
ghl-agency init-config --client windsurf
# Cline (cline_mcp_settings.json)
ghl-agency init-config --client cline
# Zed (~/.config/zed/settings.json)
ghl-agency init-config --client zed
Copy-Paste AI Prompt
Search available tools with `ghl_agency_tools_search` for `snapshots`, enable the `governance` pack, and diff our Master Snapshot against sub-account <LOCATION_ID>.
Frequently Asked Questions
Does Cline auto-approve mutating tools?
No. Our generated `cline_mcp_settings.json` only places read-only discovery tools (`ghl_agency_connection_health`, `ghl_agency_tools_search`, `ghl_agency_tools_enable`) in `alwaysAllow`; all writes require explicit approval.