If you run more than one ClickFunnels workspace, you already know the math. Six clients. Fifteen support tickets. Three logins per day per account. A password manager that has become its own job. Every small task — a tag fix, a refund, a contact lookup, a new product across three accounts — costs you a tab switch and ten minutes you do not have.

I built CF MCP because I was the one drowning in those tabs. Now it is the way I run my agency.

Here is what it is, how it works, and why it changes the operator math for anyone who runs ClickFunnels for a living.

CF MCP is a Model Context Protocol server. If that phrase does not mean anything to you yet, here is the short version: MCP is the open protocol that lets AI assistants like Claude, Cursor, and Claude Code call real tools on your behalf. Not "ask the AI and it gives you a suggestion." More like "ask the AI and it actually does the work in the system."

CF MCP is the server that connects every ClickFunnels workspace you manage to that AI. You authorize each workspace with one click. The AI then has 95+ tools available — create products, list contacts, refund orders, enroll students, draft blog posts, fire webhooks — across every account you operate, from one conversation.

It is not an integration. It is not a Zapier zap. It is the entire ClickFunnels operator surface, exposed to your favorite AI, behind one authentication flow.

If you operate a single ClickFunnels account, the platform UI is fine. You log in, you do your thing, you log out.

But if you operate six? Or fifteen? Every small task multiplies. A client emails: "Did Maria's order go through?" Now you log into their workspace, navigate to orders, search for Maria, open the order, find the transaction, check the invoice, and copy-paste it back to the client. Five minutes of clicking for thirty seconds of actual answer.

With CF MCP, that same question becomes: "Did Maria's order go through in the acme-co workspace?" Three tool calls later, you have the order, the transaction, the invoice, and a draft reply. Total time: under a minute. No tab switching. No login dance. No client password shared in Slack.

That is the actual unlock. Not a chatbot. Not a "smart assistant." A workflow shortcut for people who have done the same fifteen-click sequence a thousand times and finally have a way to skip it.

CF MCP exposes 95+ tools across the full operator surface of ClickFunnels 2.0:

Anything you can do in the ClickFunnels UI, you can describe to your AI and have it executed.

This is the piece that took the longest to get right, and the piece most agencies will care about most.

Each workspace authorizes CF MCP independently through OAuth. Your client clicks a link, approves access, done. From that point forward, the workspace shows up in your MCP session as a named context. You can list connected workspaces, switch between them with a sentence, and revoke any of them instantly from inside ClickFunnels.

No shared logins. No "send me your password." No "let me into your account real quick." The auth is per-workspace, scoped, encrypted, and revocable. If you have ever had the awkward client conversation about why you still have access to their account three months after the project ended, this fixes that.

Spin up a product across three workspaces. Describe the offer once. CF MCP creates the product, the variants, the prices, and the tags in each workspace, in sequence, with confirmations between steps. What used to be a three-tab marathon is one conversation.

Answer a support ticket without leaving the chat. A client question lands in your inbox. You ask the AI to look it up. It pulls the contact, the orders, the transaction history, and drafts a reply in your voice. You review, paste, send. Two minutes start to finish.

Ship a course in one conversation. Create the course shell, add modules, draft the lessons, enroll your beta list. Instead of opening seventeen modals to do what should take five minutes, you describe the structure and watch it build.

CF MCP is not built for everyone. If you run one ClickFunnels account for your own business and you are happy with the UI, you do not need this.

It is built for:

If you have ever caught yourself thinking "I just want to describe what I need and have it happen" — CF MCP is the tool that gets you there.

CF MCP is LLM-agnostic. It runs on the open Model Context Protocol, which means it works with Claude (web, desktop, mobile), Claude Code, Cursor, ChatGPT with MCP support, and anything else that speaks the protocol. Same server URL, every client. No SDK to install, no glue code to write.

Personally, I run it inside Claude for ops work and Claude Code for anything that touches building, scripting, or scheduled tasks. Same workspaces, same tools, two interfaces — pick the one that fits the moment.

CF MCP is currently in private access. Pricing and seat structure are shared during onboarding, and the goal of the closed beta is to make sure every early operator has the right setup, connected workspaces, and a working AI client before being turned loose.

If you want in, [request access on the CF MCP page](https://www.cfnerds.com/mcp). The onboarding is short — connect your first workspace, install the server in your AI client, and you will be running commands inside of five minutes.

CF MCP is not an official ClickFunnels product. It is an independent server built by me, Carlos Vargas, at Bezalel Digital, on top of ClickFunnels' public APIs. ClickFunnels is a trademark of Etison LLC, and CF MCP is not affiliated with or endorsed by them. It is just the tool I wanted to exist, made public.

If you run ClickFunnels for a living, this is the tool that gives you your time back. Stop clicking. Start commanding.

[Request access to CF MCP](https://www.cfnerds.com/mcp)

Carlos Vargas is the founder of Bezalel Digital. He has built ClickFunnels tooling for years — extensions, plugins, GHL migrations, and the Cloudflare-native operator stack. CF MCP is the tool he wanted, made public.