ghl

This MCP server provides a comprehensive GoHighLevel (GHL) integration, exposing tools to manage contacts, conversations, calendars, opportunities, payments, and workflows via the MCP protocol. It supports both Private Integration tokens and OAuth 2.0 for multi-account access, with built-in rate limiting and structured, type-safe tool definitions. You can configure it in your MCP client to call tools like ghl_create_contact, ghl_get_contact, ghl_send_message, ghl_create_appointment, ghl_create_opportunity, ghl_create_order, ghl_get_workflows, and many more as documented in the server's capabilities. The server is designed to work smoothly with Vercel MCP deployments and includes thorough error handling to surface actionable messages when things go wrong.

Prerequisites:

• Node.js and npm installed on your machine
• Git installed (if cloning repository)
• Access to a GoHighLevel account for credentials (Private Token or OAuth credentials)

Installation steps:

1. Install the MCP server package (example shown as a local install or global install):

npm install ghl-mcp-server

or

npm install -g ghl-mcp-server

2. Prepare environment variables. Copy the provided example and fill in credentials:

cp .env.example .env

Edit .env with either the Private Integration token or OAuth credentials:

GHL_PRIVATE_TOKEN=your_private_integration_token_here
GHL_CLIENT_ID=your_oauth_client_id
GHL_CLIENT_SECRET=your_oauth_client_secret

3. Run the MCP server locally to verify:

npm install
npm run dev

If using the example MCP client configuration, you can point to the local server or use npx as shown in the Quick Start.

Notes and tips:

• The server enforces rate limits automatically (100 requests per 10 seconds, 200k per day). If you receive 429 errors, respect the limits or enable adaptive throttling if supported by your client.
• Private Integration tokens are recommended for single-account setups; OAuth is preferred for multi-account or marketplace integrations.
• When deploying to Vercel, ensure environment variables are configured in Vercel's dashboard; the MCP integration is designed to work out of the box with Vercel deployments.
• If you encounter authentication errors, verify that your token or OAuth scopes include the necessary permissions for the requested resources (contacts, messages, calendars, opportunities, payments, workflows).
• The provided toolset includes methods grouped by domain (contacts, conversations, calendar, opportunities, payments, workflows). Use the examples in the README as a reference for how to structure tool calls in your MCP client.