Through the public GoHighLevel API and every MCP server built on it, no option can author a workflow, free or paid. The API exposes exactly one workflow operation and it is a read. The original official MCP server exposes none at all. That is the wall, it belongs to the API rather than to any one server, and the only ways past it go around the public API entirely.
GoHighLevel's public API exposes exactly one workflow operation and it is a read. The original official MCP server exposes none at all. Creating or changing a workflow through the API has been asked for repeatedly on GoHighLevel's own ideas board and has not shipped.
Every free server on this page reaches GoHighLevel through the same public API, so every one of them inherits the same ceiling. A server cannot expose a capability the API underneath it does not have, and the newer endpoint does not change it. One community repository on this list does reach past the ceiling, by driving GoHighLevel's undocumented internal API instead of the public one, which is the exception that shows where the line actually sits. So if something tells you it builds GoHighLevel workflows, it is not using the public API to do it. Ask what it is using instead, and ask what it does after the write to prove the thing it built actually opens and runs.
The Workflows section of the public API is a single read endpoint, GET /workflows/. There is no POST, PUT, PATCH or DELETE for a workflow definition. The only workflow verbs live under Contacts and enrol or remove a contact from an existing automation. This is the ceiling every column in the market map sits under.
Source: https://marketplace.gohighlevel.com/docs/ghl/workflows/get-workflow/. checked 6 Aug 2026. Re-checked 6 August 2026.
Workflow CRUD via API (Public REST and MCP support) is an open, unshipped request on HighLevel's own ideas board, posted 16 May 2026. It records that creating a workflow returns 404 and that there is no endpoint to update a workflow definition.
Source: https://ideas.gohighlevel.com/highlevel-mcp/p/workflow-crud-via-api-public-rest-mcp-support. posted 16 May 2026, open. Re-checked 6 August 2026.
A second, separate open request for the same capability (API endpoints POST, PUT and DELETE for workflows), 25 votes, dated 19 February 2026. Two independent open requests is stronger evidence than one.
Source: https://ideas.gohighlevel.com/apis/p/api-endpoints-post-put-del-for-workflows. posted 19 Feb 2026, open. Re-checked 6 August 2026.
The original /mcp/ endpoint exposes no workflow tools at all. Not read-only workflow tools. None.
Source: https://help.gohighlevel.com/support/solutions/articles/155000005741-how-to-use-the-highlevel-mcp-server. page updated 9 Jul 2026. Re-checked 6 August 2026.
Of all the operations reachable through the newer v2 endpoint, the only one that touches workflows is a read. The newer endpoint reaches hundreds of operations across dozens of domains and not one of them creates a workflow. More tools is not the missing ingredient. The write does not exist.
Source: https://marketplace.gohighlevel.com/docs/other/mcp. checked 6 Aug 2026. Re-checked 6 August 2026.
Every fact above is dated and carries its own source. If HighLevel adds workflow building, this is the first section on this site that changes, and the change is logged with the date.
There is a way past the ceiling that costs nothing, and this directory would rather tell you about it than have you find it later and wonder what else went unsaid. BusyBee3333 / Go-High-Level-MCP-2026-Complete registers create, update, delete, publish and clone tools for workflows, and it reaches them through GoHighLevel's undocumented internal API rather than the public one. Its own entry carries the evidence and the date.
That is not a loophole anyone gets for free, though, and the price is not money. An undocumented internal interface carries no compatibility promise, so it can change without a release note and take your automation with it. This one also authenticates with a credential its own setup documentation never mentions, so following its README produces a token those tools cannot use. And it ships the same non-commercial licence as its parent, which is the question to answer before running it for a paying client.
So the honest shape of it is this. The public API has no workflow write. Going around the public API is possible, and doing it in a way you can rely on next quarter is the part that costs something.
If your job is to read contacts and reply from Claude, none of this matters and you should stop here. The free options do that job and cost nothing on top of an account you already pay for.
If the job is to have the automation built, not just read, that capability is not on the public API, so it is not free. A paid server can author native GoHighLevel workflows by driving the same interface the builder uses, then reading each write back to confirm it opens, populates and runs. That is the line, and it is an honest one.
The first link is a Real Wave property that compares GoHighLevel MCP servers side by side. The second is the paid product this directory is sponsored by. Both are labelled.
Back to the list of every option. 18 of them, filterable, each carrying the date it was last checked.
MCP is the Model Context Protocol. An MCP server exposes tools an AI client like Claude, ChatGPT or Cursor can call. A GoHighLevel MCP server exposes GoHighLevel actions as those tools, so the AI can look up a contact or move an opportunity without you clicking through the interface.
No. HighLevel ships it as part of the platform. You issue a private integration token and point your AI client at it. If reading and updating records is all you need, use it.
No. Workflows are exposed read only. Workflow CRUD via API is an open, unshipped request on HighLevel's own ideas board, which is where the claim is sourced rather than asserted.
About 36 on the original endpoint at the last check, on 6 August 2026. The newer v2 endpoint exposes six meta-tools fronting a much larger operation set instead. HighLevel ships changes, so treat any exact number as dated.
Not from one token. Private integration tokens are scoped per location, so a fleet means a token per location and no single view across them.
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