01
Add the server to your MCP client
Funneled runs as a local stdio MCP server, published on npm as @getfunneled/mcp. Register it with your client using the command below — no URL or API key required.
Funneled MCP · Connect
Connect your AI agent to Funneled
The Funneled MCP server lets an MCP-compatible client — Claude Code, Claude Desktop, Cursor, or a custom agent — work directly with your funnels, analytics, products, campaigns, and A/B tests. Add it in one command, approve access once, and start working.
Claude Code
claude mcp add getfunneled -- npx -y @getfunneled/mcp Any MCP client (stdio command)
npx -y @getfunneled/mcp Three steps to connect
02
Approve access once
The first time your client calls Funneled it shows an approval link and a device code. Open the link, sign in to Funneled, and confirm the code. This one-time step needs a human — an agent cannot approve itself.
03
Start working
The access token is saved locally at ~/.config/getfunneled/mcp.json. Your agent can now inspect funnels, pull analytics, manage campaigns, and prepare changes inside the account you approved.
Configuration
Use your client's standard MCP config
Most MCP clients accept a JSON config that names the server and its launch command. Funneled is a stdio
server, so you do not point your client at a URL — the package handles authentication and routing for you.
Name the server getfunneled.
mcp config (e.g. claude_desktop_config.json, .cursor/mcp.json)
{
"mcpServers": {
"getfunneled": {
"command": "npx",
"args": ["-y", "@getfunneled/mcp"]
}
}
} Once connected
What your agent can do
Check which Funneled account and clients are available
Pull analytics summaries, time series, breakdowns, and custom reports
Find funnels, campaigns, permalinks, products, themes, and files
Create, rename, move, and open funnels in the browser
Upload local images and videos into Funneled
Select products and themes for a funnel draft
Edit draft content — block fields, global fields, sections, and order
Create and manage permalinks
Create, inspect, update, and deactivate A/B tests
Try asking your agent
Show me last week's analytics for this client.
Find the funnel for our summer campaign and open it.
Upload these product images to Funneled.
Create a permalink for the new advertorial funnel.
Set up an A/B test for this funnel with a cloned variant.
Reference
Endpoints & hosts
You normally only need the install command. These are the underlying hosts for reference — each does a different job, so don't treat any single one as "the MCP URL".
Install command
npx -y @getfunneled/mcp The stdio MCP server you run from your client.
Protocol endpoint
https://api.getfunneled.com/mcp Where the local package proxies JSON-RPC traffic. You do not call this directly.
Approval page
https://admin.getfunneled.com/mcp Where a human approves the device code on first use.
Desktop bundle source
https://mcp.getfunneled.com/manifest.json Asset and update host for the MCPB desktop bundle — not the protocol endpoint.
Want the bigger picture on why this matters for growth teams? See MCP for growth teams.
Connection FAQ
Add the Funneled MCP server to any MCP-compatible client using the stdio command "npx -y @getfunneled/mcp" and name the server "getfunneled". In Claude Code you can run "claude mcp add getfunneled -- npx -y @getfunneled/mcp". Other clients use their standard MCP config with the same command.
Funneled MCP runs as a local stdio server (the @getfunneled/mcp npm package), so you do not point your client at a URL. The package handles authentication and proxies protocol traffic to https://api.getfunneled.com/mcp on your behalf. The asset host https://mcp.getfunneled.com only serves the desktop bundle and update manifest, not protocol traffic.
No API key. The first time your MCP client uses Funneled it shows an approval link and a device code. A human opens the link, signs in to Funneled, and confirms the code once. The access token is then stored locally at ~/.config/getfunneled/mcp.json. This one-time approval cannot be fully automated by an agent.
Any client that supports stdio MCP servers, including Claude Code, Claude Desktop, Cursor, and custom agents built on the MCP SDK. Configure it as a standard MCP server with the command "npx -y @getfunneled/mcp".
Run "npx -y @getfunneled/mcp --reset-auth" to make the server request approval again, then re-approve the new device code. You can revoke a device any time from the MCP Access screen inside Funneled.
Get started
Put an AI operator inside Funneled
Connect your agent in one command, or book a demo to see how teams use MCP to prepare campaigns and inspect funnels inside Funneled.