MCP server

The FunnelFox server connects your AI tool to FunnelFox. You describe what you want in plain words, and the AI reads your funnels and data, makes the changes, and reports back. The server works with Claude Code and any AI tool that supports remote MCP servers with sign-in. Unlike AI Chat in Editor, it runs outside FunnelFox, in the AI tool you already use.

The MCP server is in Beta. Tools, permissions, and limits may change.

How MCP works

Your AI tool, such as Claude Code, Claude Desktop, or Cursor, connects to other apps through MCP servers. Each server gives it a set of actions, called tools, for one product. The FunnelFox MCP lets your AI tools list, read, and change funnels, and to read products, profiles, sessions, and transactions. This makes your AI tool a new interface for FunnelFox. Instead of clicking through the dashboard and the Editor, you hand the AI a task and it does the work:

Bulk edits in seconds: The AI works on several funnels in parallel. In one test, it created 100 checkouts on each of 3 funnels, 300 in total, in 63 seconds.
Your own context and skills: Point the AI at any files on your computer: screenshots, call transcripts, spreadsheets, specs, or research. It uses them to build and change funnels, and follows the custom skills you set up in your AI tool.
All your services in one session: Connect FunnelFox next to other MCP servers, such as Amplitude or Stripe. The AI reads FunnelFox profiles, sessions, and transactions next to their data, so you test hypotheses faster.
Turn market insights into your next launch: The AI reads competitor brands, funnels, and Meta ads from FunnelFox Market Radar. It breaks a competitor funnel down screen by screen, so you can build your own on what the market already runs.
Funnels from references: Give the AI screenshots of a funnel you like, and it rebuilds the screens in FunnelFox with your copy and styles. Background images aren’t recreated, so add your own.
Funnel structure for automation: The AI reads a funnel’s screen IDs, answer options, and navigation. Use them to match funnel screens in other systems, such as your email automation.

Nothing goes live on its own. Every save is a new unpublished version, and your live funnel changes only when you publish it in the Editor.

The MCP server can’t:

Publish funnels.
Edit your project theme.

Funnels in an older design format need to be opened once in the Editor before the AI can work on them.

MCP server setup

Choose how you connect.

Use the Claude Code plugin. It gives the AI the context it needs to edit funnels well and checks every design with the Editor’s own validator before uploading it.

Before you start, make sure you have:

20 or later on your

Install the plugin

From a in Claude Code, run:

/plugin marketplace add fnlfx/ai
/plugin install funnelfox

Run /mcp, choose plugin:funnelfox:funnelfox, then Authenticate. Your browser opens FunnelFox, where you pick the organization and permissions, then click Approve.From a shell, run claude mcp login plugin:funnelfox:funnelfox.

Get your first result

Run /funnelfox:start. Pick a funnel, then choose a conversion review, a copy rewrite in a new tone, or a rebrand to your colors.

The plugin adds these on top of the server:

/funnelfox:start: A guided first run with screenshots of the result. Tone rewrites and rebrands happen on a copy, so your original funnel stays untouched.
Editing : Rules for changing a design safely. The AI touches only what the request needs and keeps navigation, prices, and legal copy intact.
Designing skill: Guidance on what makes a funnel convert without hurting trust. It loads for review, improve, or design requests, not for plain edits.
Designer : Does the funnel work in its own context, so large designs stay out of your conversation, and returns a short report of what changed.
Local files: The design, its structure overview, and screenshots are saved in a funnelfox/ folder in your project. ignores the folder, and you can delete it anytime.

Connect the server directly, without the plugin.

Add the server

In a , run:

claude mcp add --transport http funnelfox https://mcp.funnelfox.com/mcp

Add --scope user to use the server in every project, not only the current folder.

Start Claude Code, run /mcp, choose funnelfox, then Authenticate. Your browser opens FunnelFox, where you pick the organization and permissions, then click Approve.

Add the server

Open Cursor Settings > Tools & MCP and click New MCP Server. This opens your mcp.json file. You can also edit it directly: ~/.cursor/mcp.json for all projects, or .cursor/mcp.json in one project.Add the FunnelFox server inside mcpServers:

{
  "mcpServers": {
    "funnelfox": {
      "url": "https://mcp.funnelfox.com/mcp"
    }
  }
}

Back in Tools & MCP, click Connect next to funnelfox. Your browser opens FunnelFox, where you pick the organization and permissions, then click Approve.

Use it in chat

Open the chat in mode and ask Cursor to list your FunnelFox funnels.

The Codex CLI and the Codex IDE extension share one file, so you set up the server once for both.

Add the server

In a terminal, run:

codex mcp add funnelfox --url https://mcp.funnelfox.com/mcp

Or add it to ~/.codex/config.toml yourself. In the IDE extension, open it from the gear menu: MCP settings > Open config.toml.

[mcp_servers.funnelfox]
url = "https://mcp.funnelfox.com/mcp"

Run:

codex mcp login funnelfox

Your browser opens FunnelFox, where you pick the organization and permissions, then click Approve.

Use it

Start Codex and ask it to list your FunnelFox funnels.

In VS Code, MCP servers work in Chat.Follow the Codex tab instead if you use the Codex extension in VS Code.

Add the server

Open the , run MCP: Add Server, and choose HTTP. Paste the server URL and name the server funnelfox.

https://mcp.funnelfox.com/mcp

Choose where to save it: Copilot Global for all workspaces, or .mcp.json for the current workspace only.You can also create .mcp.json in your workspace root yourself:

{
    "mcpServers": {
    "funnelfox": {
    "type": "http",
    "url": "https://mcp.funnelfox.com/mcp"
}
}
}

When the server first starts, confirm that you trust it. VS Code then asks you to sign in. Allow it, and your browser opens FunnelFox, where you pick the organization and permissions, then click Approve.

Use it in chat

Open the Chat view and ask Copilot to list your FunnelFox funnels.

Any AI tool that supports remote () MCP servers can connect. If your tool supports OAuth sign-in, add the server URL https://mcp.funnelfox.com/mcp and sign in when it asks. If it doesn’t, connect with an . A token reaches only the project you create it in.

Create a token

In FunnelFox, go to Settings > API keys > MCP tokens and click New token.

Set up the token

Name: What the token is for, for example the machine it lives on.
Permissions: Pick at least one. You only see the permissions your own role includes.
Expires in: 30, 90, or 365 days.

Click Create token, then copy the token.

Add the server

In your AI tool’s MCP settings, add the server URL with this :

URL:    https://mcp.funnelfox.com/mcp
Header: Authorization: Bearer <token>

Replace <token> with the token you copied. Many tools use a JSON config like this one; check your tool’s docs for the exact format:

{
  "mcpServers": {
    "funnelfox": {
      "url": "https://mcp.funnelfox.com/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

The token is shown once, so copy it before you click Done. It’s stored in plain text in your AI tool’s . Keep it out of code repositories, and revoke it if it leaks.

The server sends its core editing rules to every AI tool. The skills, designer subagent, /funnelfox:start, local validation, and saved screenshots come only with the Claude Code plugin.

Permissions

You choose permissions at sign-in, or when you create an access token. A sign-in covers every project in the organization you pick, and never more than your own role allows.

Permission	Shown at sign-in as	What the AI can do
Always included	None	See your organization, your account email, the granted permissions, and the projects they apply to; find projects by name
`funnel:view`	View funnels	List and read funnels, their locales and designs; render screenshots; list templates; read Project context
`funnel:edit`	Edit funnels	Save design changes, create draft funnels, add locales
`product:view`	View products	Read products and their price lists
`customer:view`	View customers	Read profiles (email, custom user ID, country, source funnel), sessions (IP address, city, postal code, browser and device), and transactions
`analytics:view`	View analytics	List funnels and read transactions
`experiment:view`	View experiments	List funnels. Available at sign-in only
`radar:view`	View Market Radar	Search the Meta ad market and read niches, brands, competitor funnels, ads, and the project’s Radar favorites. Only for organizations with Market Radar
`radar:edit`	Edit Market Radar	Pin and unpin niches, brands, and Facebook pages in the project’s Radar favorites. Only for organizations with Market Radar
`settings:view`, `integration:view`, `billing:view`, `audit_log:view`	View project settings, View integrations, View billing, View the audit log	Nothing yet. The related tools are coming soon.

To change permissions later, sign in again. In /mcp, choose Clear authentication, then Authenticate, and check the permissions you need.

Manage access

Every sign-in and access token appears in Settings > API keys > MCP tokens. Each row shows the name, a masked hint, when it was last used, its expiry date, and its permissions. To revoke access, click Revoke next to it and confirm. Any agent using it stops working on its next call. This can’t be undone. To sign out on your machine only, choose Clear authentication in /mcp, or run claude mcp logout plugin:funnelfox:funnelfox.

Tools

These tools are called based on your request.

Tool	What it does	Permission
`project_info`	Shows your organization, granted permissions, and number of projects	Always included
`project_list`	Finds projects by name	Always included
`funnel_list`	Lists the funnels in a project	`funnel:view`, `analytics:view`, or `experiment:view`
`funnel_get`	Reads a funnel’s details and locales	`funnel:view`
`funnel_design_get`	Reads a funnel’s design	`funnel:view`
`funnel_screenshot_get`	Renders screens as images, including unsaved changes	`funnel:view`
`template_list`	Lists FunnelFox templates	`funnel:view`
`project_context_get`	Reads your Project context	`funnel:view`
`funnel_design_update`	Saves changes to a funnel’s design	`funnel:edit`
`funnel_create`	Creates a draft funnel from a template or as a copy of another funnel	`funnel:edit`
`locale_create`	Adds a locale to a funnel	`funnel:edit`
`product_list`, `product_get`	Reads products and their price lists	`product:view`
`profile_list`, `profile_get`	Reads profiles	`customer:view`
`session_list`	Reads funnel sessions	`customer:view`
`transaction_list`	Reads purchases, renewals, and refunds	`customer:view` or `analytics:view`
`radar_search`	Searches the Meta ad market by name or URL across brands, Facebook pages, funnels, and ads	`radar:view`
`radar_niche_list`	Lists market niches	`radar:view`
`radar_brand_list`, `radar_brand_get`	Reads brands with their ad channels, Facebook pages, and creative mix	`radar:view`
`radar_funnel_list`, `radar_funnel_get`	Reads competitor funnels: screens, paywall prices and PSPs, and the advertorials that send traffic to them	`radar:view`
`radar_creative_list`, `radar_creative_get`	Reads Meta ads: text, CTA, media, and run dates	`radar:view`
`radar_favorite_list`	Lists the niches, brands, and Facebook pages pinned in the project	`radar:view`
`radar_favorite_update`	Pins or unpins a niche, brand, or Facebook page	`radar:edit`

Coming soon:

Analytics: Read KPIs, charts, tables, and cohorts.
Experiments: Read experiment setup, per-variant metrics, and significance, then create, start, and stop experiments.
Customer data: Read subscriptions and funnel replies.
Funnel lifecycle: Archive, restore, and delete funnels, and roll back to an earlier version.

Usage

Name the funnel and say what you want, the way you’d brief a colleague.

Edit funnels in bulk

Hand repetitive edits to the AI instead of repeating them by hand. It works on several funnels in parallel. In one test, it created 100 checkouts on each of 3 funnels, 300 in total, in 63 seconds.

Change the same text or style across many funnels, such as a button label or a footer.
Update plan prices on every paywall, together with the legal disclosures that quote them.
Translate funnels, using your own files for tone and audience.

Analyze funnel data alongside other services

Ask questions about your FunnelFox data without copying it between dashboards or asking support for an export. The AI reads profiles, sessions, and transactions, plus the products and prices available for checkout, and combines them with data from your other MCP servers in one session.

Find the profiles that purchased, with their source funnel and country.
Compare FunnelFox transactions with Stripe payments or Amplitude events.
Check a hypothesis with a quick report instead of building a dashboard.

Build funnels from a spec

Plan and build a funnel in the same place. Point the AI at any local files, such as specs, screenshots, call transcripts, or spreadsheets, and it builds the funnel from a FunnelFox template or a copy of an existing funnel.

Hand over a spec sheet and ask the AI to build the funnel.
Share screenshots of a reference funnel, and the AI rebuilds the screens with your copy and styles. Background images aren’t recreated, so add your own.
Turn a competitor funnel analysis into a draft funnel.

The more context you give, the better the result. A funnel built without brand files, visuals, or a reference looks generic.

Turn market insights into your next launch

Research your market and build on it in one session. The AI reads the brands, competitor funnels, and Meta ads that FunnelFox Market Radar tracks, then uses them to plan and build your funnel.

Find the longest-running ads in your niche and the funnels they send traffic to.
Break a competitor funnel down screen by screen: headlines, buttons, prices, and the paywall.

Speed up experiments

Prepare experiment variants without skipping steps to save manual work.

Copy a funnel and edit the copy as the variant.
Edit variations quickly, and roll the winning change out to every locale.
Connect the Amplitude MCP server to check a hypothesis against your data before you build the variant.

Then set up and launch the experiment in the dashboard. Learn more about creating experiments.

Automate work in other systems

The AI reads a funnel’s structure: screen IDs, answer options, and navigation. Use it to connect funnels to other systems in one session.

“List the screen IDs and answer options of the Sleep quiz funnel, so I can match them in my email automation.”

Coming soon: full experiment cycles, analytics dashboards in your AI tool, funnel replies with purchase data, and test ideas from past results.

Next steps

Set up your Project context so the AI matches your brand and voice.
Run an experiment to test changes whose effect is uncertain.
Edit funnels by prompt inside FunnelFox with AI Chat in Editor.

Getting started

Agentic solution

Integrations

Editor

Dashboard

How MCP works

MCP server setup

Permissions

Manage access

Tools

Usage

Edit funnels in bulk

Analyze funnel data alongside other services

Build funnels from a spec

Turn market insights into your next launch

Speed up experiments

Automate work in other systems

Next steps

​How MCP works

​MCP server setup

​Permissions

​Manage access

​Tools

​Usage

​Edit funnels in bulk

​Analyze funnel data alongside other services

​Build funnels from a spec

​Turn market insights into your next launch

​Speed up experiments

​Automate work in other systems

​Next steps

How MCP works

MCP server setup

Permissions

Manage access

Tools

Usage

Edit funnels in bulk

Analyze funnel data alongside other services

Build funnels from a spec

Turn market insights into your next launch

Speed up experiments

Automate work in other systems

Next steps