CashClaw GHL MCP

CashClaw GHL MCP

An MCP server for GoHighLevel with 82 live-tested tools, enabling CRM operations like contact management, appointments, invoices, and workflows via natural language.

Category
Visit Server

README

CashClaw GHL MCP

The only GoHighLevel MCP server with independently verified live test coverage.

82 tools. 72/72 live-verified against a real GHL sub-account. 16 bugs found and fixed that exist in every alternative. Runs on Claude Desktop, Cursor, Windsurf, and any MCP-native agent — today.


Why this one

Every other GHL MCP connector has at least one of these problems:

Problem Who has it
269 tools registered but most silently fail to load mastanley13 (168 stars, abandoned)
Auto-generated from OpenAPI spec, zero live testing drausal (only npm package)
461 tools, maintainer unknown, no verified write coverage BusyBee3333
HTTP-only, incompatible with Claude Desktop Official GHL MCP
Maintainer redirecting users to paid SaaS mastanley13

CashClaw GHL MCP:

  • 82 tools — lean by design, every one registers and responds
  • 72/72 independent live-test passes against a real GHL sub-account (run npm test to verify yours)
  • 16 production bugs found and fixed — bugs that exist in every fork of mastanley13
  • stdio transport — works with Claude Desktop out of the box, no HTTP bridge needed
  • Actively maintained by a solo GHL operator running it in production daily

The 16 bugs fixed

Every GHL MCP forked from mastanley13 ships these broken:

  1. get_appointments — wrong URL path, always 404
  2. delete_appointment — IAM 401, missing required field
  3. create_appointment / update_appointmentappointmentStatus field rejected by GHL
  4. search_contacts — sent as GET, GHL requires POST
  5. create_contact_task — missing required completed field
  6. move_opportunity_stage — PATCH 404, GHL requires PUT
  7. Custom fields path — 403 on wrong endpoint
  8. Email templates — wrong endpoint (/emails/templates/emails/builder)
  9. Email campaigns — wrong endpoint (/emails/campaigns/emails/schedule)
  10. Payments — missing altId/altType params, returns empty
  11. create_invoice — minimal body not accepted, required fields missing
  12. send_invoice — missing userId, silently fails
  13. get_contacts / get_opportunities — pagination off-by-one, drops last page
  14. get_form_submissions — wrong page param name
  15. get_social_posts — GET endpoint, GHL requires POST
  16. trigger_workflow — timestamp format rejected (must be +00:00 not Z)

If you're using any other community GHL MCP, all 16 of these are live bugs in your setup right now.


Tools (82 total)

Module Tools
Contacts get, create, update, upsert, delete, search, add/remove tags, notes CRUD, tasks CRUD
Opportunities list, get, create, update, delete, move stage, pipeline list, pipeline summary
Conversations list, get, messages, send SMS / email / RVM, create, mark read, update status
Calendar list calendars, CRUD appointments, free slots, blocked slots
Workflows list, get by ID, trigger for contact, remove contact
Campaigns list, add contact, remove contact, fire inbound webhook
Forms list forms, get submissions
Funnels list funnels, list pages
Social list posts, create/schedule post
Payments products, orders, invoices (create/send/record payment), transactions, subscriptions
Email Marketing templates CRUD, campaigns CRUD, campaign stats
Location settings, users, custom fields/values, tags, health snapshot
Agency list sub-accounts, create sub-account

Setup

1. Get your GHL Private Integration Token

GHL → Settings → Integrations → API Keys → Create Private Integration → All scopes → Copy key.

2. Get your Location ID

It's in the URL when inside a sub-account: https://app.gohighlevel.com/location/YOUR_LOCATION_ID/...

3. Install

git clone https://github.com/centrender/ghl-mcp.git
cd ghl-mcp
npm install
cp .env.example .env
# Paste your GHL_API_KEY and GHL_LOCATION_ID into .env

4. Verify it works

npm test

72 tool probes fire against your GHL account and report pass/fail. If something is broken in your token scopes, you'll know before you start using it.

5. Connect to Claude Desktop

Mac: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "ghl-cashclaw": {
      "command": "node",
      "args": ["/absolute/path/to/ghl-mcp/src/index.js"],
      "env": {
        "GHL_API_KEY": "pit-your-key-here",
        "GHL_LOCATION_ID": "your-location-id-here"
      }
    }
  }
}

Restart Claude Desktop. Tools appear automatically.

Connect to Cursor / Windsurf

Same config format. Refer to your editor's MCP docs for the exact config file location.


Usage examples

"Give me a full snapshot of my GHL account"
"Show me all contacts tagged 'RVM Sent' added this week"
"Move opportunity [ID] to the 'Demo Booked' stage"
"Send a follow-up SMS to all contacts in stage 'Called Back'"
"List all workflows and trigger 'Scout Outreach' for contact [ID]"
"Create a contact: John Smith, 310-555-0101, tag: scout-2026"
"Create an invoice for $497 for contact [ID], due in 7 days, and send it"
"Book an appointment for [contact] tomorrow at 2pm on calendar [ID]"
"Pull revenue summary for this month"

Platform support

Platform Support Notes
Claude Desktop Native (stdio) This repo
Claude Code Native Same config
Cursor Native Same config
Windsurf Native Same config
VS Code Copilot Native Same config
ChatGPT / Gemini Via HTTP bridge Needs thin wrapper (not yet included)
LangChain / CrewAI / AutoGen Via MCP client mcp Python package

What it costs

This server: $0. Runs on your machine or any VPS.

GHL API calls are included in your GHL subscription. Hosting on Hetzner CX22 (~$4/mo) handles it with room to spare if you want it server-side.


File structure

ghl-mcp/
├── src/
│   ├── index.js            ← MCP server entry point
│   └── ghl-client.js       ← GHL REST client (429 retry, full CRUD)
├── tools/
│   ├── contacts.js
│   ├── opportunities.js
│   ├── conversations.js
│   ├── calendar.js
│   ├── automation.js       ← workflows, campaigns, forms, funnels, social
│   ├── payments.js
│   ├── email-marketing.js
│   └── location.js
├── .env.example
└── package.json

Built by

Faruk Sahin — Centrender LLC

Running this in production at VoxLead Agency for AI receptionist outreach at scale. If it breaks, I fix it — because I'm using it too.

Issues and PRs welcome.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured