HighLevel MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authenticating MCP requests via X-API-Key header. | |
| SUPABASE_URL | Yes | URL of the Supabase project (e.g., https://your-project.supabase.co). | |
| TOKEN_CACHE_TTL | No | Token cache TTL in milliseconds. | 300000 |
| CLIENT_CACHE_TTL | No | Client mapping cache TTL in milliseconds. | 600000 |
| HIGHLEVEL_API_BASE | No | Base URL for HighLevel API. | https://services.leadconnectorhq.com |
| SUPABASE_SERVICE_KEY | Yes | Supabase service role key for database access. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivitySlowing
ResponsivenessNo issues