Choosing a server is only half of it. The other half is whether the AI app you use can actually connect to it. The official server needs a token sent in a header, and some apps have no place to put one. When that happens the connection just will not work, no matter how many times you paste the address.
Choosing a server is half of it. The other half is whether the AI client you use can actually connect to the thing you chose. The official HighLevel server authenticates with a token in a header; some clients let you set arbitrary headers and some do not. A client that only offers OAuth fields has nowhere to put a token.
| Client | Free to use | Custom header | Notes |
|---|---|---|---|
| Claude Code | Paid Claude plan | Yes | Adds an HTTP server with one command and takes a header flag. The most forgiving client on this list. |
| Claude, web and desktop | Custom connectors available across plan tiers | Not in custom connectors | Custom connectors expose OAuth fields only, so a token needs a local bridge instead. Connections also originate from Anthropic's servers, which matters if you allowlist by address. |
| Cursor | Free tier | Yes | A JSON file per project or per user. Remote servers take a URL and an optional headers block. Top level key is mcpServers. |
| VS Code | Free | Yes | A JSON file in the workspace. Top level key is servers, which differs from Cursor's mcpServers. A common copy and paste failure. |
| ChatGPT | Requires developer mode and a qualifying plan | depends | Not verified OpenAI's own documentation and widely repeated third party guides disagree about which tiers get write access. We are not repeating either until we have checked it in product. |
| n8n | Free self hosted | one header reliably | Not verified The official server needs two headers and this is a known sore point. See the n8n entry above. |
This is why the newer OAuth capable endpoint matters more than its release note suggested. For some clients it is the difference between working and not working. Checked 6 August 2026.
The client question is about reach, not capability. A perfectly connected client still cannot make a server author a workflow over the public API, because the write does not exist there.
This is the ceiling every option on this list that reads and acts runs into, and it belongs to the API rather than to this one project. Where free stops sets out why, with five dated sources you can open yourself.
Every option on this page, checked the same way, with the date each one was last looked at. It moves: licences change, repositories go quiet, and HighLevel ships things that move the wall. Leave an address and the changes come to you, instead of you re-checking every one of them yourself.
One email when something here changes. Nothing else, ever.
One email per change, with an unsubscribe link in every one. Real Wave pays for this list, so the address sits in Real Wave's system and is used for exactly this.
Prefer people to email? Join Real Wave AI on Facebook