Log inSubmit server
Leadconnector logo

Leadconnector

Connects AI agents to GoHighLevel CRM data for contacts, pipelines, opportunities, and campaigns.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Leadconnector

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "leadconnector": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-leadconnector"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y @pipeworx/mcp-leadconnector

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 5d ago.

Overview

The Leadconnector MCP server connects AI agents to a GoHighLevel or LeadConnector CRM account through five read-oriented tools. It searches and retrieves contacts, lists pipelines and opportunities, and returns campaign records using a caller-supplied GoHighLevel token. Use it when an agent needs to inspect CRM records, sales pipeline data, or campaign information. It is available through a Pipeworx gateway endpoint or as a local stdio package.

Use cases

  • Search contacts by name, email, or phone
  • Inspect a contact’s CRM details and custom fields
  • Review pipelines and their sales stages
  • List opportunities for a selected pipeline
  • Find campaign names and statuses

Key features

  • Contact search and retrieval
  • Pipeline and stage listing
  • Opportunity listing by pipeline
  • Campaign listing
  • Hosted gateway and local stdio modes

Tools5

What Leadconnector lets your agent do. Expand a tool for its parameters.

Self-reported~382 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

8/8 checks healthy over the last 51d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · @pipeworx/mcp-leadconnector (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads471Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed5Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Leadconnector works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Leadconnector

Leadconnector is an MCP server that connects AI agents to GoHighLevel or LeadConnector CRM accounts. Its main tools search and retrieve contacts, list sales pipelines and opportunities, and list marketing or automation campaigns. Calls use the caller’s GoHighLevel token through the `_apiKey` argument, with `locationId` required for v2 `pit-` tokens.

Install it locally by configuring an MCP client to run `npx -y @pipeworx/mcp-leadconnector`. The package communicates over stdin and stdout and does not require a Pipeworx gateway account. You can also connect to the hosted endpoint at `https://gateway.pipeworx.io/leadconnector/mcp`.

Yes, Cursor is named in the repository as an MCP client for this server. Add either the hosted MCP URL or the local `npx` command to Cursor’s MCP configuration, then provide `_apiKey` and, when applicable, `locationId` in tool calls.

First call `leadconnector_list_pipelines` to obtain a pipeline ID, then pass that ID to `leadconnector_list_opportunities`. The opportunity response includes deal value, stage, status, and the associated contact, and both calls require the appropriate GoHighLevel credential.

Related MCP servers

All in Customer Data Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLeadconnector AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/leadconnector?style=directory)](https://allmcps.com/mcp/leadconnector)
HTML Embed
<a href="https://allmcps.com/mcp/leadconnector"><img src="https://allmcps.com/api/badge/leadconnector?style=directory" alt="Leadconnector on AllMCPs" /></a>