Skip to content
ClickFunnels Help CenterClickFunnels Help CenterClickFunnels Help CenterGo to CF Classic Help Center

Which ClickFunnels integration should I use?

Published: Updated:

ClickFunnels has four ways of connecting. They are not alternatives to one another: each solves a different problem. Choose which one based on your use case.

The four surfaces

Section titled “The four surfaces”
Surface What it is Runs where Auth
REST API v2 HTTP endpoints for your ClickFunnels data Your server or personal computer Team API access token, or OAuth 2.0 to act for other users
Page SDK A script that makes a web site or app you host behave like a funnel Your web site/app’s HTML pages cfp_ page token in a meta tag (public, scoped to that one page)
MCP Server An AI-assistant connector for your workspaces Claude, on behalf of one human Interactive OAuth consent; the user picks which workspaces to grant
Webhooks ClickFunnels calls you when something happens Your server or personal computer Endpoints are registered through the REST API

Community support

Section titled “Community support”

At the moment there is no first-party ClickFunnels API client library. To call the API, you make plain HTTP requests. Packages on npm and RubyGems with “clickfunnels” in the name are community projects, not maintained by ClickFunnels. If you came here looking for “the ClickFunnels SDK for Node/Ruby/Python”, you want the REST API. See also Accessing the ClickFunnels API.

The REST API cannot take a card payment on your own checkout UI. There is no “charge this card” endpoint for a page you host. Selling from a page you host means the Page SDK, and only the Page SDK. The API can record external purchases (creating Order and Invoice records) and it can manage live orders — refund, cancel, update.

Pick by what you’re doing

Section titled “Pick by what you’re doing”

“My app has its own database and I just want to push leads into ClickFunnels.” → REST API. Create or update the contact, apply tags. No page involved, no browser involved. The SDK is the wrong tool here — it requires a registered page and it takes over form submission.

“I want to read orders/customers to build a dashboard.” → REST API, with expand[], filtering, and pagination. Use MCP for ad-hoc exploration, but don’t build a product surface on it.

“I want to sell something from a page I host myself externally, for example on Vercel, Lovable or Netlify.” → Page SDK. This is the only path for a checkout UI on a page you host. The REST API cannot process a card payment on your own checkout. The SDK mounts the payment gateway UI, prices the cart server-side (tax, discounts, shipping), handles 3-D Secure, supports order bumps, and supports one-click one-time offers against the saved card.

“I have a landing page on my own domain and I want it to work like a funnel step.” → Page SDK. Visit tracking and contact identity carried across steps on different domains are SDK-only capabilities.

A page does not have to be a funnel step to be registered. You can register a standalone external page — tracked immediately — and place it into a funnel later, including into a conditional split branch or a split-test variant. Note that SDK checkout and form submission require placement, and return page_not_in_funnel until the page is a step, so it knows where to redirect your visitors.

“I’m moving an external page to a different domain.” → See the Migrate an External Page Domain skill.

“I want to build funnels or pages programmatically.” → REST API, MCP, and/or the Page SDK, depending on who is doing the work and where the pages live. Use the API or MCP to create and manage funnel structure from your system or an agent; use the Page SDK when the pages themselves are hosted outside ClickFunnels.

“I want Claude to manage my workspace for me.” → MCP Server. Natural language, no code. You pick which workspaces to grant access to. See ClickFunnels MCP Server.

The current server exposes 12 tools (create, fetch, list, update, destroy, take_action, read_action, describe_category, list_workspaces, switch_workspace, current_workspace, dispatch) using progressive discovery over a runtime catalog — not a flat list of one tool per resource. Older write-ups describing ~130 individual tools are describing the legacy server.

“I’m building a product that acts on behalf of other ClickFunnels users.” → REST API + OAuth 2.0. Reach for MCP when an agent is doing the work for a human who granted it access; reach for the API when your system is doing the work.

“I want to react when something happens in ClickFunnels.” → Webhooks. See Creating Webhooks in ClickFunnels.

“I’d rather not write code at all.” → ClickFunnels Workflows, native integrations, or Zapier. See No-Code and Low-Code.

What each one cannot do

Section titled “What each one cannot do”
  • The REST API cannot take a card payment on your own checkout UI. There is no “charge this card” endpoint for a page you host — that is the Page SDK. The API can record external purchases (creating Order and Invoice records) and it can manage live orders — refund, cancel, update.
  • The Page SDK cannot run server-side. It is browser-only, tied to a specific registered page, and it owns form submission on that page.
  • MCP is for agents, not for system-to-system integration. Consent is granted by a human in their own AI assistant.
  • Workspace selection is the MCP scoping mechanism. You choose which workspaces to grant during consent. A workspace grant can be Read and Write or Read Only. There is also per-category scoping — Read and Write / Read Only / No access.

Gating and status

Section titled “Gating and status”
  • MCP Server — available to any user who administers at least one team. Public client registration is open. The current connector URL is https://agents.myclickfunnels.com/mcp. The legacy connector at https://mcp.myclickfunnels.com/sse still works if you already have it connected, but it does not include the new tools — disconnect and reconnect to get them. See ClickFunnels MCP Server.
  • SDK access — invite-only, and covers external pages and checkout together. There is no state where you have external pages but not checkout. Request access at code support.
  • REST API v2 and webhooks — generally available. API access follows plan availability.

Authentication at a glance

Section titled “Authentication at a glance”
Surface Auth
REST API — your own workspace Team API access token
REST API — acting for other users OAuth 2.0
Page SDK cfp_ page token in a meta tag (public; scoped to that one page)
MCP Interactive OAuth consent; user selects which workspaces to grant

Where to go next

Section titled “Where to go next”