Before connecting an assistant, finish this sentence: “I want to do this work, in this product, for this workspace.”
That sentence matters when a teammate sends a ClickFunnels link, a support article mentions AI, and your assistant shows a connection named ClickFunnels. The names alone do not tell you whether all three point to the same place.
ClickFunnels AI at clickfunnels.ai is a separate product from ClickFunnels 2.0. A ClickFunnels 2.0 account is not required for CFAI. If you intend to work on an existing CF2 funnel, keep using its existing links. The CFAI agent guide explains the product boundary and current access conditions.
Use the process below to identify the right destination. Then follow that product's setup instructions. Download the connection-identity worksheet to record the decision and anything still unknown.
Start with the work you intend to do
Write one specific task. “Use AI” is too broad. These are clearer:
- Prepare the offer and page brief for a new CFAI project.
- Revise the opening copy of the team's existing CF2 webinar funnel.
- Find out which workspace owns a page before assigning someone to edit it.
For new CFAI work, start with the public CFAI planning guide. Reading it does not require builder access. If the homepage shows “Coming soon,” the guide says that building, signup, templates and browser approval of an MCP connection are not open in that browser. You can prepare the brief while access remains unavailable. Do not treat a connection URL as a way around that gate. CFAI access and connection guidance
For an existing funnel, record its product, workspace and current editor link from the person responsible for it. A public page address, screenshot or familiar funnel name is not enough to identify the editable project. If the owner is unknown, make finding the owner the next task.
The result of this step should be a target you can describe without mentioning an AI client.
Separate the product from the way you reach it
There are three questions to answer:
| Question | What to record |
|---|---|
| Which product owns the work? | CFAI, the existing ClickFunnels platform, Classic, or unresolved. |
| Which workspace owns the target? | A team or workspace label confirmed by its owner; unknown if you have no workspace yet. |
| How do you intend to work? | Planning only, a feature inside the product, or an external assistant connection. |
The existing ClickFunnels platform has documentation called “Build with AI.” It describes an assistant inside that product's workspace dashboard. Finding that article does not make it a CFAI setup guide. Follow its own documentation when that is the product you intend to use. Existing-platform Build with AI documentation
An external assistant connection is another choice. MCP is a way for an assistant to communicate with a service. The assistant's name does not identify the service it will reach, and a friendly connection label is not a substitute for checking the configured server address.
If a teammate says “connect ClickFunnels,” ask for the intended product, workspace and current official setup page. That is enough information to resolve the destination before changing a connection.
Match the complete server address
When external MCP is the intended route, compare the full server address with the documentation for the product you selected.
| Documented destination | Server address |
|---|---|
| ClickFunnels AI | https://www.clickfunnels.ai/mcp |
| Existing ClickFunnels platform, current MCP endpoint | https://agents.myclickfunnels.com/mcp |
| Existing ClickFunnels platform, legacy MCP endpoint | https://mcp.myclickfunnels.com/sse |
This reference was checked on October 7, 2026. The existing-platform MCP page was updated September 16, 2026 and identifies its current and legacy addresses. Neither is the CFAI endpoint. Recheck the CFAI guide or the existing-platform MCP documentation before actual setup.
Check the hostname and path, including /mcp or /sse. If your saved connection points somewhere else, record the mismatch. Do not rename the connection and assume its destination changed.
A legacy address is useful identity evidence. It is not, by itself, a reason to remove a working team connection. Ask its owner which setup instructions apply before changing shared work.
For intentional existing-product work, the official CF2 sign-in and Classic sign-in are separate destinations. Use the one that belongs to your existing work. This guide does not establish which account contains your funnel or whether you can access it.
Record what the evidence actually establishes
Keep these states separate in the worksheet:
- Documented: an official page identifies the product and endpoint.
- Observed by you: you inspected your actual connection settings or confirmed the intended workspace with its owner. Write down exactly what you saw.
- Unknown: you have not established an account, workspace, access level or connection result.
- Mismatch: the selected product and configured destination do not agree, or the available evidence conflicts.
Those labels describe individual fields, not a blanket pass for the whole project. You might know the correct endpoint while workspace access remains unknown.
A matching address does not establish successful authorization. Successful access to one product does not establish access to another. Do not infer CFAI permissions, plans or credits from an existing-product account or support page. Use the selected product's current access information.
For CFAI, use the agent guide when you are ready for client setup and verification. It owns those instructions. This worksheet helps you arrive there with the right target; completing it does not connect an account or verify a build.
Fictional example: planning a new CFAI project
Maya is preparing a new workshop offer for CFAI. She has no existing funnel to edit. A search brings her to the existing platform's “Build with AI” article, while the CFAI homepage in this scenario shows “Coming soon.”
Her decision record reads:
| Field | Maya's entry |
|---|---|
| Intended work | Prepare the offer, audience and page brief for a new CFAI project. |
| Product | CFAI. No existing-product funnel is part of this task. |
| Workspace | Unknown; none established for this scenario. |
| Route now | Public CFAI planning guide. |
| Documented MCP destination |
https://www.clickfunnels.ai/mcp; reference only, no connection attempted. |
| Access evidence | Hypothetical “Coming soon” screen; builder and MCP approval unavailable in that browser. |
| Next action | Finish the brief and check current CFAI access guidance before setup. |
Maya does not switch to a CF2 signup just because that support page also mentions AI. Her useful output today is a clear brief. The worksheet records access as unresolved for future setup, without making a connection claim.
Fictional example: intentional work on an existing CF2 funnel
Eli needs to revise the opening copy for a funnel labeled “Autumn Session.” Its owner confirms that it belongs to the team's existing CF2 workspace, “Workshop Team.” Those labels are invented for this example.
Eli sees a saved assistant connection named ClickFunnels. Its configured server is https://mcp.myclickfunnels.com/sse.
His decision record reads:
| Field | Eli's entry |
|---|---|
| Intended work | Revise opening copy on the existing Autumn Session funnel. |
| Product and workspace | CF2, Workshop Team; owner confirmation is an assumption in this fictional case. |
| Current connection evidence | A legacy existing-platform endpoint, according to its official documentation. |
| CFAI relevance | No CFAI project is part of this task. |
| Access and execution | Authorization, available actions and changes remain unverified. |
| Next action | Confirm the intended connection with the owner and read the current existing-platform instructions before changing setup. |
Eli can also ask whether the intended approach is the existing product's built-in AI. That choice belongs to the existing-product task and its access documentation. Neither path establishes that a CFAI connection was made, and the example performs no edit.
Leave an unresolved decision with a specific next action
You do not need to guess when the evidence is incomplete. Write the missing fact and who can supply it:
“The funnel owner has not confirmed the product or workspace. Ask the owner for the current editor destination before selecting an assistant connection.”
Use the worksheet to capture the task, product, workspace, official source, configured endpoint if known, and remaining uncertainty. Give the next step an owner. Once those fields agree, continue with the selected product's current setup instructions.