GoHighLevelGoHighLevel MCP server

GoHighLevel MCP Server for any AI client.

NotFair connects your GoHighLevel sub-account to Claude, Codex, Cursor, and any MCP client — 35 tools to explore contacts, conversations, and pipelines, and stage approved CRM updates.

View setup guide

No credit card required · Read live data, approve every write

Works with
GoHighLevel MCP
Live

MCP endpoint

https://notfair.co/api/mcp/gohighlevel
OAuth 2.0Streamable HTTP

Live tools

35

New to MCP? Read the spec at modelcontextprotocol.io.

Tools exposed

35GoHighLevel tools your AI client can read and act on

Broad read tools across your CRM plus bounded write tools scoped to the locations you connect.

ToolType
listLocationsRead
listContactsRead
listConversationsRead
listOpportunitiesRead
listCalendarEventsRead
listUsers / listPipelines / listCalendarsRead
and more CRM, calendar, and payments tools

Connect HighLevel and try it in Claude

Authorize NotFair to read your HighLevel CRM, then add the MCP server to Claude. The first prompt to try: "summarize my last 50 conversations and flag the unanswered ones."

Read the Claude connector setup guide

FAQ — NotFair MCP server

Common questions about authenticating, configuring, and using the NotFair GoHighLevel MCP server.

It's a remote MCP (Model Context Protocol) server at https://notfair.co/api/mcp/gohighlevel that exposes your HighLevel CRM as typed read and write tools for AI agents. Claude Desktop, Claude.ai Web, Claude Cowork, Claude Code, and Codex can all connect to it and work with live CRM data.

Two paths. Claude.ai's Add custom connector flow uses OAuth 2.0 with PKCE — no Client ID or Secret to copy. CLI clients (Claude Code, Codex, custom) use a personal access token (PAT) you mint from the connect page; pass it as `Authorization: Bearer ghl_pat_*`. Tokens are scoped to a single HighLevel connection (Company or Location) and are revocable.

Yes. When an agency installs the app via the Marketplace flow with bulk installation enabled, NotFair fans out per-location tokens automatically and exposes each location as its own MCP connection. PATs and Claude OAuth tokens scope to a single connection so you can keep agency-wide and per-location access separate.

Locations, contacts, conversations and message history, opportunities by pipeline, calendars and events, users, custom fields, tags, tasks, forms, surveys, workflows, invoices, payments, products, custom objects, and related CRM metadata. Tokens are encrypted at rest and refreshed server-side via HighLevel's standard refresh flow.

Yes. The GoHighLevel connector exposes bounded mutation tools for contacts, opportunities, calendar appointments and events, tags, and contact tasks. The generic `request` escape hatch remains read-only.

From /connect/gohighlevel: each connection has a Disconnect button that removes the local row and revokes both Claude OAuth tokens and personal access tokens. HighLevel's UNINSTALL webhook does the same automatically if you remove the app from inside HighLevel.