This MCP server provides programmatic access to your GoHighLevel (GHL) CRM via the Model Context Protocol (MCP). It exposes a wide range of GHL endpoints and capabilities as modular tools that can be orchestrated through natural-language prompts. With this server, you can request actions such as querying contacts, creating and updating opportunities, scheduling appointments, sending messages, and managing blog content, all through AI-driven commands. The design emphasizes a foundation that exposes ALL sub-account level endpoints, enabling you to build automations that combine GHL with other tools and data sources for workflows like lead qualification, outreach sequencing, and reporting.

To use it, start the MCP server according to the installation instructions, then send requests that map to GHL API actions. Tools are organized around GoHighLevel resources (contacts, opportunities, calendars, invoices, blogs, workflows, etc.). You can chain actions across tools (for example, search contacts, create an opportunity for a found contact, and schedule an appointment) to build powerful, context-aware automations. The server is intended as an extensible foundation for experiments, learning, and building custom AI-powered automations on top of your GHL account.

Prerequisites:

• Node.js (recommended LTS) and npm installed on your system
• Access to a GoHighLevel Private Integrations API key and a Location ID

Installation steps:

1. Clone the repository: git clone https://github.com/mastanley13/GoHighLevel-MCP cd GoHighLevel-MCP

2. Install dependencies: npm install

3. Configure environment variables:

   • PRIVATE_INTEGRATIONS_API_KEY: Your GoHighLevel Private Integrations API key
   • LOCATION_ID: Your GoHighLevel Location ID
   • GHL_API_BASE_URL: Base URL for GHL API (if applicable)
   • LOG_LEVEL: (optional) info|warn|error

4. Start the server: npm start

   or if using direct node approach from the mcp_config:

   node server.js

5. Verify startup by checking logs and visiting the local endpoint configured by the server. Ensure your Private API key has the required scopes listed in the README (contacts, conversations, opportunities, calendars, blogs, invoices, payments, products, etc.).

Tips and caveats:

• This project exposes a wide surface area of the GHL API. Implement proper safeguards and least-privilege access for production use.
• Use the provided environment variables to secure sensitive keys and control behavior (e.g., LOG_LEVEL for log verbosity).
• If you need more scopes, update your Private Integration in GoHighLevel and restart the MCP server.
• Monitor rate limits; implement backoff strategies in your orchestrations if you plan multiple concurrent operations.
• The repository is described as a foundational/open architecture; extend the client types and modules as needed for customization and security hardening.