# Leadconnector [Health: Active]

**Category:** 👤 Customer Data Platforms  
**Repository:** https://github.com/pipeworx-io/mcp-leadconnector  
**GitHub Stars:** 0  
**npm Downloads (last month):** 471  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/leadconnector

## Description
LeadConnector / GoHighLevel MCP Pack — wraps the GoHighLevel CRM for AI agents.

## Tools
Capabilities this server exposes over MCP:

- **leadconnector_list_contacts** — Search or list CRM contacts in a GoHighLevel/LeadConnector account. Free-text query matches name, email, or phone. Returns a {contacts:[...], meta} envelope with contact IDs, names, emails, phones, tags, and custom fields. Requires your own GoHighLevel token via _apiKey (plus locationId for a v2 `p…
- **leadconnector_get_contact** — Fetch a single CRM contact by its contact ID. Returns full detail: name, email, phone, tags, source, custom fields, and timestamps. Requires your own GoHighLevel token via _apiKey (plus locationId for a v2 `pit-` token).
- **leadconnector_list_pipelines** — List all sales pipelines and their stages in the account. Returns a {pipelines:[...]} envelope with pipeline IDs, names, and ordered stages. Use the returned pipeline ID with leadconnector_list_opportunities. Requires your own GoHighLevel token via _apiKey (plus locationId for a v2 `pit-` token).
- **leadconnector_list_opportunities** — List opportunities (pipeline deals) for a given pipeline. Requires a pipelineId (get one from leadconnector_list_pipelines). Returns deals with monetary value, stage, status, and the associated contact. Requires your own GoHighLevel token via _apiKey (plus locationId for a v2 `pit-` token).
- **leadconnector_list_campaigns** — List marketing/automation campaigns in the account. Returns a {campaigns:[...]} envelope with campaign IDs, names, and status. Useful for finding a campaign to attribute or enroll contacts. Requires your own GoHighLevel token via _apiKey (plus locationId for a v2 `pit-` token).

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "leadconnector": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-leadconnector"]
  }
}
```

## Documentation

## What the Leadconnector MCP server does

The Leadconnector MCP server exposes selected GoHighLevel CRM operations through the Model Context Protocol. Its tools focus on reading account data rather than changing records. Agents can search contacts by free text, retrieve an individual contact, inspect sales pipelines and stages, list opportunities within a pipeline, and list marketing or automation campaigns.

Contact results can include IDs, names, email addresses, phone numbers, tags, and custom fields. Individual contact responses add information such as source and timestamps. Pipeline responses contain pipeline identifiers, names, and ordered stages. Opportunity results include deal value, stage, status, and the related contact. Campaign results include campaign identifiers, names, and status.

## How it works

The Leadconnector MCP server can be connected through the Pipeworx hosted endpoint at `https://gateway.pipeworx.io/leadconnector/mcp`. A client sends normal MCP initialization, tool-listing, and tool-call requests to that endpoint. The pack endpoint exposes the LeadConnector tools and also includes shared Pipeworx meta-tools, including tools for discovery, search, memory, and routing questions across the broader catalog.

The same functionality is available as a local stdio process through `@pipeworx/mcp-leadconnector`. In that mode, the process communicates over standard input and output and lists only the pack’s five tools. The hosted and local options use the same tool set, but only the gateway connection provides the shared gateway meta-tools.

Some operations depend on earlier results. For example, call `leadconnector_list_pipelines` to obtain a pipeline ID before calling `leadconnector_list_opportunities` for that pipeline. The gateway also supports `ask_pipeworx`, which lets an agent describe a LeadConnector data request in plain language instead of selecting a pack tool directly.

## Setup and configuration

For a hosted connection, add the pack URL to an MCP client configuration. For local use, run the package with `npx -y @pipeworx/mcp-leadconnector` and configure the client to launch that command. The repository names Claude Desktop, Cursor, and Windsurf as supported setup targets.

Each CRM tool requires the caller’s own GoHighLevel credential through the `_apiKey` argument. Requests using a v2 `pit-` token also require `locationId`. These values are request parameters, not documented process environment variables. The hosted endpoint does not provide an API key on the user’s behalf.

## Tools and capabilities

- `leadconnector_list_contacts`: Search or list contacts, with free-text matching across names, emails, or phone numbers.
- `leadconnector_get_contact`: Fetch complete details for a contact ID.
- `leadconnector_list_pipelines`: Return sales pipelines and their ordered stages.
- `leadconnector_list_opportunities`: Return opportunities for a specified pipeline.
- `leadconnector_list_campaigns`: Return marketing or automation campaigns and their statuses.

## Limitations and notes

Opportunity listing requires a pipeline ID, so an agent normally needs to discover pipelines first.

A gateway connection exposes more tools than the five LeadConnector tools because shared Pipeworx meta-tools are included. The exact scope should be taken from the connection’s `initialize` response. Use the local stdio package when you want only the pack tools and no gateway account or gateway round trip. Both modes still require suitable GoHighLevel credentials when calling CRM tools.

_Full upstream README: https://allmcps.com/mcp/leadconnector/readme_