Funnel Pulse MCP

@funnelpulse/mcp is the thin local MCP wrapper over the Funnel Pulse API.

It does not contain Funnel Pulse business logic. It translates MCP tool calls into authenticated HTTP requests against the public API, so the durable contract remains the Funnel Pulse API rather than a second hosted control plane.

Who this is for

Use this package when you want Claude, VS Code, Cursor, Windsurf, or another MCP-capable client to work with your Funnel Pulse account through a local MCP process.

The local MCP process stays thin:

• it authenticates with your Funnel Pulse API key
• it exposes MCP tools to your AI client
• it forwards those tool calls to the Funnel Pulse API

Requirements

• Node.js 20+
• a Funnel Pulse API key
• optional: FUNNEL_PULSE_API_URL if you are not using the default API base URL

Quick start

Run without a permanent install:

npx -y @funnelpulse/mcp

Or install it globally:

npm install -g @funnelpulse/mcp
fp-mcp

Environment variables

• FUNNEL_PULSE_API_URL defaults to http://localhost:5095
• FUNNEL_PULSE_API_KEY is required

Client configuration

Most MCP clients now provide a UI or CLI command for adding servers. When they ask for the command, arguments, and environment variables, use these values:

• command: npx
• args: -y @funnelpulse/mcp
• env:
  • FUNNEL_PULSE_API_URL=https://api.funnelpulse.io
  • FUNNEL_PULSE_API_KEY=fpsa_...

If your client still uses a JSON config file, this is the server entry to paste in:

{
  "mcpServers": {
    "funnel-pulse": {
      "command": "npx",
      "args": ["-y", "@funnelpulse/mcp"],
      "env": {
        "FUNNEL_PULSE_API_URL": "https://api.funnelpulse.io",
        "FUNNEL_PULSE_API_KEY": "fpsa_..."
      }
    }
  }
}

If you install the package globally instead of using npx, the same entry becomes:

{
  "mcpServers": {
    "funnel-pulse": {
      "command": "fp-mcp",
      "env": {
        "FUNNEL_PULSE_API_URL": "https://api.funnelpulse.io",
        "FUNNEL_PULSE_API_KEY": "fpsa_..."
      }
    }
  }
}

Available tools

• funnels.list
• funnels.get
• flowtrace.map.get
• flowtrace.map.discover
• flowtrace.settings.update
• flowtrace.runs.list
• flowtrace.run.get
• flowtrace.run.queue

What to ask your AI client

After the MCP server is connected, common requests look like this:

• "List my Funnel Pulse funnels"
• "Get the FlowTrace map for funnel <id>"
• "Enable FlowTrace protection for funnel <id> with a daily schedule"
• "Queue a FlowTrace run for funnel <id>"
• "Show me the latest FlowTrace runs for funnel <id>"

Troubleshooting

• If the MCP client says the process could not be started, verify Node.js 20+ is installed and available on your PATH.
• If tool calls fail with authentication errors, verify FUNNEL_PULSE_API_KEY is present and current.
• If tool calls fail with connection errors, verify FUNNEL_PULSE_API_URL points to the correct Funnel Pulse environment.
• If the MCP server starts but no useful data comes back, confirm the API key belongs to the organization you expect.

Development

cd packages/mcp
npm install
npm run build