HighLevel MCP Server

Multi-account HighLevel CRM MCP server with OAuth integration for managing 30+ sub-accounts through a unified interface.

Overview

This MCP (Model Context Protocol) server enables AI agents like TypingMind, ClickUp Brain, and other MCP clients to interact with multiple HighLevel CRM sub-accounts through a single unified interface. Instead of managing 30+ Private Integration Tokens (PITs), this server leverages your existing OAuth tokens stored in Supabase.

Key Features

• 🔐 OAuth Integration - Uses existing access tokens from Supabase
• 🏢 Multi-Account Support - Manage 30+ HighLevel sub-accounts through one connection
• ⚡ 18 Read-Only API Tools - Contacts, conversations, opportunities, calendars, locations, payments, and utilities (write operations disabled by default)
• 🔌 Dual Transport - Streamable HTTP (POST /mcp) for modern clients + legacy SSE (GET /sse) for TypingMind
• 🚀 Cloudflare Workers - Serverless, stateless session handling across worker isolates
• 💾 Smart Caching - 5-minute token cache for optimal performance
• 🎯 Client-Friendly - Use client names or location IDs interchangeably
• 📋 Calendar Discovery - get-calendars / calendars_get-calendars tools plus auto-discovery in calendars_get-calendar-events

Why This Exists

HighLevel's official MCP server requires one Private Integration Token (PIT) per sub-account. For agencies managing 30+ clients, this means:

• ❌ Manually creating 30+ PITs through the UI
• ❌ Managing 30+ separate MCP connections
• ❌ No programmatic token management

Our solution:

• ✅ Reuse existing OAuth tokens from your Supabase database
• ✅ One MCP connection for all clients
• ✅ Automatic token management with caching

Architecture

┌──────────────────────────────┐
│  AI Clients                  │
│  (TypingMind, ClickUp, etc.) │
└──────────────┬───────────────┘
               │ MCP Protocol
               │  • Streamable HTTP → POST /mcp
               │  • Legacy SSE      → GET /sse
               │
┌──────────────▼────────────────────────┐
│ Cloudflare Worker                     │
│ ┌───────────────────────────────────┐ │
│ │ Token Manager (5min cache)        │ │
│ └───────────────┬───────────────────┘ │
│                 │                       │
│ ┌───────────────▼───────────────────┐ │
│ │ 18 Read-Only API Tools            │ │
│ └───────────────┬───────────────────┘ │
└─────────────────┼─────────────────────┘
                  │
          ┌───────▼────────┐
          │   Supabase     │
          │ ┌────────────┐ │
          │ │ locations  │ │
          │ │ - access_  │ │
          │ │   token    │ │
          │ └────────────┘ │
          └────────────────┘
                  │
          ┌───────▼──────────────┐
          │ HighLevel REST API   │
          │ 30+ Sub-Accounts     │
          └──────────────────────┘

Endpoints

Endpoint	Method	Purpose
/	GET	Health check (no API key required)
/mcp	POST	Streamable HTTP MCP transport (ClickUp, modern clients)
/mcp	DELETE	Terminate MCP session
/sse	GET	Legacy SSE connection (TypingMind)
/sse	POST	Direct MCP message (no session)
/sse/message	POST	MCP message with SSE session

Health check response includes version, toolCount, calendarTools, and available endpoints.

MCP protocol version: 2025-03-26 (previously 2024-11-05)

Authentication: All endpoints except / require an API key via the X-API-Key header.

Session handling: Streamable HTTP uses stateless Mcp-Session-Id headers (no in-memory session store), which is required for Cloudflare Workers where requests may hit different isolates.

Available Tools (18 Read-Only)