What Clickfunnels exposes
I get programmatic access to ClickFunnels through three channels: an official MCP server at clickfunnels.com/mcp, a REST API documented at clickfunnels.com/developers, and native Zapier and Make connectors. The API covers the platform's core objects (funnels, contacts, orders, products, courses, and customers) with a Node SDK available for server-side work. The MCP server lets me wire ClickFunnels directly into Claude, Cursor, or any MCP-compatible client without writing glue code. Zapier and Make handle the no-code automation layer across thousands of downstream apps. Authentication details and webhook availability aren't published in the data I have, so confirm those in the developer docs before building. No direct ChatGPT or Claude plugin integrations are listed beyond MCP.
Access, auth, and limits
The ClickFunnels MCP server is a beta release (a Technical Preview, in their words: core features functional, some capabilities still being perfected). It connects over Server-Sent Events at https://mcp.myclickfunnels.com/sse. What you get for that connection is wide: 80+ tools covering Contacts (10), Opportunities and Sales Pipelines (13), Courses (10), Orders and Transactions (15), and Products (20), plus Webhooks, Forms, Images, and Workspace and Teams management.
One gap to flag honestly: the ClickFunnels docs do not publicly spell out the authentication method for the MCP server yet. I'm not going to guess at a flow that isn't documented, so confirm the exact auth setup in their MCP documentation before you wire it into a production client. Beta status means that detail (and others) can shift, so check the current docs at connection time rather than trusting a snapshot.
Where it works and what to build
Today the supported client is Claude Desktop, and you need a paid Claude plan to use it: Pro, Max, Team, or Enterprise. That's the whole compatibility story for now, so if your AI stack runs on something other than Claude Desktop, this MCP server isn't a fit yet. For a Claude user, setup is the usual MCP connector flow pointed at the SSE endpoint.
Once it's connected, the workflows that make sense track the daily reality of running a funnel business. Ask Claude to pull this week's recent orders, spot the customers who bought a front-end offer, and create a follow-up product to upsell them. Or have it scan your sales pipelines, list the opportunities stuck in one stage too long, and draft outreach. Or point it at a course and ask it to check enrollment and recent activity. Because the server reaches contacts, orders, products, courses, and pipelines, you can chain a read across several of those in one prompt instead of clicking through five dashboard screens. Beta caveat still applies: treat these as prototypes, not load-bearing automations, until it leaves preview.
Which AI clients can use Clickfunnels MCP?
Not every AI assistant supports MCP natively. Per-client picture for Clickfunnels:
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | The only supported MCP client today. Requires a paid Claude plan (Pro, Max, Team, or Enterprise). Connects over SSE at https://mcp.myclickfunnels.com/sse. |
| Claude Code | Not supported | Not listed as a supported client for the ClickFunnels MCP beta yet. |
| ChatGPT | Not supported | Not listed as a supported client for the ClickFunnels MCP beta yet. |
| Cursor | Not supported | Not listed as a supported client for the ClickFunnels MCP beta yet. |
| Gemini | Not supported | Not listed as a supported client for the ClickFunnels MCP beta yet. |
How to connect Clickfunnels MCP to Claude Desktop
Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.
{
"mcpServers": {
"clickfunnels": {
"command": "npx",
"args": ["mcp-remote", "<YOUR_MCP_URL>"]
}
}
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://mcp.myclickfunnels.com/sse
// Claude Code (one-liner): claude mcp add clickfunnels <YOUR_MCP_URL> --transport httpSome MCP servers require an API key. Check the source page for setup: mcp.myclickfunnels.com/sse.
Does Clickfunnels MCP cost extra?
Clickfunnels ships an official MCP server that uses your existing subscription credentials.
- No separate MCP licence to buy. You pay for your Clickfunnels plan, the MCP server queries that account.
- Whether it's gated to a specific tier wasn't extracted automatically — verify the access requirements on the MCP page or pricing docs.
Clickfunnels subscription pricing
| Plan | Monthly | Annual / mo |
|---|---|---|
| Launch | $97 | $81 |
| Scale | $197 | $164 |
| Optimize | $297 | $248 |
| Dominate | — | $500 |
Source: clickfunnels.com/pricing. Verified 2026-06-07.
Clickfunnels also publishes a REST API
Clickfunnels publishes an API, but per-tier gating wasn't extracted automatically.
What you can do with Clickfunnels from an AI agent
Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.
Skip the dashboard, ask Claude
- "What changed this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe Clickfunnels data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's Clickfunnels account
- Multi-account workflows without context-switching the Clickfunnels UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage Clickfunnels data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production Clickfunnels safe
Limits and gotchas
- Official MCP server — published by Clickfunnels themselves, so it should track product changes.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Rate limits: MCP calls count against your underlying Clickfunnels API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Score: 6/10 on MCP-readiness. ClickFunnels ships an official MCP server with broad coverage: 80+ tools spanning contacts, sales pipelines, courses, orders, and products, which is more of the platform than most beta MCP servers expose. It loses points because it's still a beta Technical Preview (capabilities can change) and because Claude Desktop, on paid Claude plans, is the only supported client today. Single-client plus beta keeps this out of the 8-plus range, but the tool breadth is what pulls it up to a 6 rather than down with the thin previews.
Strong agent fit with an official MCP server in technical preview. ClickFunnels exposes a Labs MCP endpoint (mcp.myclickfunnels.com) with roughly 100 tools across contacts, orders, products, courses, and webhooks, backed by a published OpenAPI spec, an llms.txt index, webhooks, and a Node SDK. The caveats are real: it is beta and currently Claude Desktop only, so treat it as early but legitimate.
Scored 2026-06-07 by Joonas (TMB).
Clickfunnels MCP & API FAQ
Is the Clickfunnels MCP server official?+
Can I use the Clickfunnels MCP with Cursor or Codex?+
Does Clickfunnels have a public API?+
Sources
- Clickfunnels official site: https://www.clickfunnels.com/
- MCP server page: https://mcp.myclickfunnels.com/sse
- API docs: https://www.clickfunnels.com/developers
- Pricing source: https://www.clickfunnels.com/pricing (verified 2026-06-07)
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.