Connecting Claude to LeadConnector MCP

Claude Code (CLI) — Already Done on This Box

The server is already installed and connected on the Hetzner fleet:

claude mcp add --transport http leadconnector https://services.leadconnectorhq.com/mcp/anthropic/v2

Verify: claude mcp list — should show leadconnector: ... Connected

Or via .mcp.json in a project root:

{
  "mcpServers": {
    "leadconnector": {
      "type": "http",
      "url": "https://services.leadconnectorhq.com/mcp/anthropic/v2"
    }
  }
}

On first use, Claude Code opens a browser for LeadConnector OAuth authorization.

Claude.ai

1. Open Claude.ai → Settings → Connectors → Add custom connector
2. Set server URL: https://services.leadconnectorhq.com/mcp/anthropic/v2
3. Click Connect and complete sign-in (sign in, pick sub-account, approve)
4. Start a new chat — tools are now available

Test: "Find the last 5 contacts I added in LeadConnector"

Claude Cowork

1. Open connectors/integrations settings in Claude Cowork
2. Add custom connector
3. Server URL: https://services.leadconnectorhq.com/mcp/anthropic/v2
4. Complete LeadConnector sign-in and pick sub-account

Using a Private Integration Token (PIT)

Instead of OAuth, pass a PIT in the Authorization header:

Authorization: Bearer pit-your-token

Create the token under Settings → Private Integrations in your GHL account, selecting the exact scopes needed. PIT has a more limited scope set than OAuth.

Permissions & Security

• One sub-account per connection — you choose which location at connect time.
• Scoped to your grant — the assistant can only perform operations your OAuth or PIT scopes allow.
• Safety checks — sensitive/irreversible operations have additional confirmation steps built in.
• Revoke access at any time from your LeadConnector account settings.