CLICKFUNNELS PRODUCT AND CONNECTION IDENTITY WORKSHEET Purpose: identify the intended product, workspace and way of working before following setup instructions. Completing this worksheet does not connect an account, establish permission, run a tool or verify a build. Use a new record for each target project. Keep passwords, OAuth codes, tokens, customer data and private sign-in links out of the worksheet. A team alias and non-sensitive project label are enough for a shared planning record. STATUS KEY (apply to each field, not the whole project) DOCUMENTED: an official source describes the product or destination. OBSERVED BY YOU: state precisely what you inspected or whom you confirmed it with. UNKNOWN: evidence has not established this fact. MISMATCH: the selected product and configured destination disagree, or evidence conflicts. Resolve the conflict before proceeding with that setup. BLANK DECISION RECORD Record label: Recorded by: Decision date and timezone: 1. TASK AND TARGET Specific work to do: New CFAI planning / intentional existing-product work / unresolved: Existing artifact label, if any: Intended product (CFAI / existing CF2 / Classic / unresolved): Product identity evidence and field status: Person who can confirm the product and target: 2. WORKSPACE AND WAY OF WORKING Workspace or team alias (UNKNOWN if not established): Who confirmed it, when, and what was confirmed: Planning only / built-in product feature / external assistant / unresolved: Why this route fits the task: 3. SOURCE AND CONNECTION IDENTITY Official setup or access source URL: Source publication/update date (UNKNOWN if not provided): Date you checked the source: Client or assistant name, if relevant: Saved connection label, if relevant: Actual configured server address (UNKNOWN if not inspected): Documented server address for intended product: Exact hostname and path match? YES / NO / UNKNOWN / NOT APPLICABLE: Connection identity evidence and field status: 4. ACCESS AND EVIDENCE LIMITS What current product/access screen or owner evidence establishes: What account or workspace access remains UNKNOWN: Authorization or successful read evidence, if separately obtained: UNKNOWN / NOT PERFORMED unless you have actual evidence; describe it narrowly. Build or change evidence, if separately obtained: UNKNOWN / NOT PERFORMED unless you have actual evidence; describe it narrowly. Do not infer CFAI permissions, plans or credits from an existing-product account. 5. DECISION AND NEXT ACTION Outcome: CFAI planning / identified existing-product task / unresolved: What agrees (task, product, workspace, documentation, configured destination): What conflicts or remains unknown: Next action: Person responsible: Date to revisit: If unresolved, use a specific request: "Please confirm the product, workspace and current editor destination for [project label]. I need that target before choosing its assistant connection." ENDPOINT REFERENCE -- CHECKED OCTOBER 7, 2026 This is an identity reference, not a setup recipe or verification of your access. Check the current official page before actual setup. A saved connection name is not evidence of the configured server. Compare the complete hostname and path. ClickFunnels AI: https://www.clickfunnels.ai/mcp Current guidance: https://www.clickfunnels.ai/agents Machine guidance: https://www.clickfunnels.ai/skill.md Existing ClickFunnels platform, current MCP endpoint: https://agents.myclickfunnels.com/mcp Existing ClickFunnels platform, legacy MCP endpoint: https://mcp.myclickfunnels.com/sse Source: https://support.myclickfunnels.com/docs/clickfunnels-mcp-server/ Published February 13, 2026; updated September 16, 2026. Neither existing-platform endpoint is the CFAI endpoint. Existing-platform built-in AI documentation: https://support.myclickfunnels.com/docs/build-with-ai/ Published June 16, 2026; updated September 16, 2026. This describes a feature in that product's workspace, not CFAI setup. Do not remove a working legacy team connection solely because this reference labels it legacy. Confirm the intended setup with the connection owner. FICTIONAL FILLED EXAMPLE A: NEW CFAI PLANNING Person and task: Maya prepares an offer, audience and page brief for a new CFAI workshop project. No existing funnel is part of the task. Intended product: CFAI. Workspace: UNKNOWN; none established in this fictional case. Way of working now: public CFAI planning guide. Documentation: https://www.clickfunnels.ai/agents Documented server: https://www.clickfunnels.ai/mcp Actual configured server: UNKNOWN; no connection attempted. Access evidence: the CFAI homepage hypothetically shows Coming soon. The guide says building, signup, templates and browser approval of an MCP connection are not open in that browser. This is a scenario assumption, not an actual test. Authorization/read/build: NOT PERFORMED. Decision: finish the CFAI brief; do not switch product because another support page mentions AI. Next action: Maya checks current CFAI access guidance before attempting setup. Future workspace and account access: UNKNOWN. FICTIONAL FILLED EXAMPLE B: INTENTIONAL EXISTING CF2 WORK Person and task: Eli revises opening copy for Autumn Session in Workshop Team. All people, workspace labels and project labels here are fictional. Intended product: CF2, confirmed by the owner as an assumption in this scenario. Way of working under consideration: existing external assistant connection. Connection label: ClickFunnels. Configured server in this scenario: https://mcp.myclickfunnels.com/sse Official documentation: https://support.myclickfunnels.com/docs/clickfunnels-mcp-server/ Identity conclusion: documentation identifies it as a legacy existing-platform endpoint. It is not the CFAI destination. Current endpoint in the same documentation: https://agents.myclickfunnels.com/mcp Authorization, available actions and successful reads: UNKNOWN / NOT PERFORMED. Changes or builds: NOT PERFORMED. Decision: stay with the intentional existing-product task. Do not change or remove a team connection merely because a newer endpoint is documented. Next action: Eli confirms the intended connection with its owner and reads the current existing-platform instructions. If built-in AI is the intended route, use that product's feature and access documentation instead. CFAI account, credits or connection conclusions: none established by this case. HANDOFF CHECK [ ] The task names a concrete project or a new planning deliverable. [ ] Product identity has evidence, or UNKNOWN is explicit. [ ] Workspace identity has evidence, or UNKNOWN is explicit. [ ] Built-in AI and external MCP are treated as different ways of working. [ ] The official source belongs to the selected product. [ ] A configured endpoint is exact, UNKNOWN or NOT APPLICABLE, never guessed. [ ] Documentary identity is separate from authorization/read/build evidence. [ ] No account, plan or credit entitlement is inferred across products. [ ] Remaining uncertainty has a next action and an owner. [ ] No credentials or private customer details are in this record.