Clarflow MCP Server
Connect Clarflow to Claude, Cursor, or any AI tool that speaks the Model Context Protocol and manage your whole workspace in plain language — build a quiz funnel, publish it, read the drop-off, launch an A/B test.
There is nothing to install and no key to copy. Clarflow hosts the server; you add its URL to your tool and sign in to Clarflow.
- Server URL —
https://mcp.clarflow.com - Transport — Streamable HTTP
- Authentication — OAuth: your tool opens a browser, you sign in to Clarflow, pick a workspace, and click Allow
What you can do
Once connected, you can ask for things like:
- "Build me a 6-step skincare quiz that segments by skin type, then publish it."
- "Which step of my supplement quiz is losing the most people?"
- "What are people actually answering on question 3?"
- "Set up a 50/50 A/B test between my two landing quizzes."
- "Add three more questions to the end of my collagen funnel."
The quick way
- Open Clarflow and go to Settings → API & MCP.
- Pick your tool — Claude Code, Cursor, Claude (web & Desktop), or something else.
- Follow the two or three steps shown: add the server (one command, one click, or one URL), then sign in when your tool asks.
The connection appears under Connected tools as soon as you've signed in. To disconnect, click Remove connection — it stops working immediately, and your tool will ask you to sign in again next time.
What a connection can do
A connection is a personal credential: it acts as you, in one workspace, with whatever permissions you have right now.
| Your workspace role | What a connection from your account can do |
|---|---|
| Owner / Admin | Everything below |
| Editor | Create, edit, publish, duplicate, and delete funnels |
| Analytics | Read funnels and analytics only — every write is refused |
Because the role is read live on every request, a connection automatically loses access when you are removed from the workspace or your role is reduced. There is nothing to clean up.
A connection can never: touch billing, manage members, or reach any other workspace.
Connecting manually
The same steps Settings → API & MCP shows, for reference.
Claude Code
claude mcp add --transport http --scope user clarflow https://mcp.clarflow.com
Then, inside Claude Code, run /mcp, pick clarflow, and choose Authenticate. Sign in to Clarflow in the browser, choose a workspace, and click Allow.
--scope user makes it available in every project. --scope project shares it with your team through the repo's .mcp.json — safe to commit, since it contains only the URL; each person signs in as themselves.
Cursor
Add this to ~/.cursor/mcp.json (or use Add to Cursor in Settings → API & MCP):
{
"mcpServers": {
"clarflow": {
"url": "https://mcp.clarflow.com"
}
}
}
Then open Cursor Settings → MCP and click Connect (or Needs login) next to clarflow, and sign in.
Claude (claude.ai and Claude Desktop)
- Open Settings → Connectors → Add custom connector.
- Enter the URL
https://mcp.clarflow.comand click Add. Leave Advanced settings empty. - Click Connect, sign in to Clarflow, choose a workspace, and click Allow.
Any other MCP client
Add https://mcp.clarflow.com as a remote (Streamable HTTP) server. Clients that support MCP authorization will open a browser for you to sign in. Clients that can only run local servers can bridge through mcp-remote, which handles the sign-in too:
{
"mcpServers": {
"clarflow": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.clarflow.com"]
}
}
}
Connected with an API key before? Existing
cf_live_keys keep working until you remove them in Settings → API & MCP. New connections all use sign-in.
Tools
| Tool | Reads / writes | What it does |
|---|---|---|
get_workspace_info | read | Which workspace, acting as whom, and exactly what this connection may do |
get_funnel_schema | read | The funnel JSON reference, by section |
list_funnels | read | Every funnel with publish state and live URL |
get_funnel | read | One funnel — a step outline, or the full document |
create_funnel | write | New funnel, optionally with all its steps |
update_funnel | write | Append steps, or replace all of them |
duplicate_funnel | write | Copy a funnel into a new draft |
delete_funnel | destructive | Permanently delete a funnel and its analytics |
get_funnel_changes | read | What publishing would do, before you do it |
publish_funnel | destructive | Push a funnel live to real visitors |
revert_funnel | destructive | Discard the draft, restore the live version |
get_funnel_analytics | read | Visitors, conversions, drop-off, devices, traffic sources |
get_question_responses | read | What visitors actually answered, per question |
get_workspace_analytics | read | Totals across every funnel |
list_ab_tests | read | Cross-funnel A/B tests and their status |
create_ab_test | write | New split test across published funnels |
manage_ab_test | destructive | Publish, pause, end, or reweight a test |
The A/B testing tools only appear if cross-funnel A/B testing is enabled on your account. If you don't see them, contact support.
Resources
Two references are also exposed as MCP resources, for clients that support them:
clarflow://schema/funnel-json— the funnel JSON formatclarflow://schema/css-classes— every CSS class a funnel exposes
A worked example
You: Build me a 6-step quiz that helps people find the right protein powder, then publish it.
The assistant will typically:
- Call
get_workspace_infoto see what it's allowed to do. - Call
get_funnel_schemato read the funnel JSON format. - Call
create_funnelwith the whole quiz. - Call
get_funnelto check the result reads well. - Call
get_funnel_changes— it will reportfirst_publish. - Call
publish_funneland hand back the live URL.
You: A week later — where is that funnel losing people?
get_funnel_analyticsreturns per-step drop-off and names the worst step.get_question_responsesshows what people picked before they left.
Working with funnel content
Funnels are built from a JSON format called clarflow-canvas-nodes — the same format the Clarflow builder accepts when you paste onto the canvas. The full reference lives at /docs/json-builder, and the assistant can fetch it itself with get_funnel_schema.
One thing worth knowing, because it trips people up: get_funnel with include: "full" returns the stored format (nodes keyed by id, edges using from/to), while the write tools take the clipboard format (arrays, edges using source/target). They are not interchangeable. If you are editing an existing funnel, prefer update_funnel with mode: "append" — it generates ids for you and never round-trips the whole document.
Safety
The assistant is driving your live account, so a few things are worth knowing before you start.
Publishing is immediate. publish_funnel puts a funnel in front of real traffic.
Structural changes reset analytics. If you change a funnel's steps, its existing results can't carry over — publishing archives them to a version and restarts collection from zero. The API refuses this until it is asked for explicitly, so the assistant has to confirm with you first.
Deleting is permanent. delete_funnel removes the funnel and its analytics with no undo.
Publishing affects live experiments. If a funnel is a variant in a running A/B test, publishing changes that experiment mid-flight. The response says so.
Your builder tab stays in sync. If you have the funnel open in Clarflow, a write through the API shows up in that tab within a second or two — no reload. If the tab has unsaved edits at that moment it asks whether to load the new version or keep yours. If someone else has the funnel open, the write is refused rather than being silently overwritten by their next autosave.
Destructive tools are marked as such in the protocol, so clients like Claude Code will ask before running them. You can Remove connection at any time from Settings → API & MCP; it stops working on the next request.
Troubleshooting
| What you see | What it means |
|---|---|
401 / "Not signed in to Clarflow" | The connection was removed. Reconnect from your tool and sign in again. |
401 / "no longer a member of this workspace" | Whoever created the connection left the workspace. Any current member can connect again. |
| "This connection acts as a workspace analytics…" | Your role can't perform that action. Ask an owner or admin. |
| "A/B testing is not enabled for this account" | The feature isn't switched on — contact support. |
| A/B tools are missing entirely | Same reason: they're only advertised when enabled. |
| "Another Clarflow user currently has this funnel open" | Close the funnel in the builder, or retry with force: true. |
| "This funnel changed since you read it" | Something else edited it. Ask the assistant to re-read and retry. |
| Nothing happens after adding the server | Restart the client. Most only read MCP config at startup. |
| The browser never opens to sign in | Trigger it from the tool: /mcp → Authenticate in Claude Code, Connect in Cursor's MCP settings. |
Support
Questions about the MCP server: support@clarflow.com.