Mcp Funnel
Consolidate many MCP servers behind one stdio endpoint with per-tool allowlists so Claude Code or Cursor stays fast and within context limits.
Overview
MCP Funnel is an MCP server for the Build phase that proxies and merges multiple MCP backends with configurable tool filtering.
What is this MCP server?
- Proxies multiple downstream MCP servers through one stdio connection
- Tool filtering and customization to trim irrelevant or risky capabilities
- Optional `.mcp-funnel.json` config path or `MCP_FUNNEL_CONFIG` env override
- npm package `mcp-funnel` with `npx -y` runtime hint (v0.0.6 package, server v0.0.7)
- Reduces duplicate server entries in Claude Desktop / IDE MCP config
- Server schema version 0.0.7 in catalog metadata
- npm package identifier `mcp-funnel` with stdio transport
- Optional positional config_path argument plus MCP_FUNNEL_CONFIG env
Community signal: 153 GitHub stars.
What problem does it solve?
Each extra MCP server multiplies tools and config noise, making agents slower, harder to secure, and painful to maintain across machines.
Who is it for?
Builders running three or more MCP servers who need allowlists, renamed tools, or a single stdio entry for local dev.
Skip if: Teams that only use one MCP server or need hosted HTTP/SSE aggregation without running a local proxy.
What do I get? / Deliverables
You register one funnel server in your agent config and route many underlying MCPs through a single filtered tool surface.
- Single stdio MCP endpoint exposing a curated subset of tools
- Centralized funnel config for repeating the same stack across dev machines
- Cleaner agent manifests with fewer duplicate or experimental tools
Recommended MCP Servers
Journey fit
Solo builders wire up agent stacks during product development; funneling servers is an integration layer before shipping features that call tools. Agent-tooling is where you compose MCP processes, filter noisy tools, and customize what the model can invoke day to day.
How it compares
MCP proxy and config layer, not a domain skill or a single-purpose API integration.
Common Questions / FAQ
Who is MCP Funnel for?
Solo builders and developers who run multiple MCP servers in Claude Code, Cursor, or similar clients and want one aggregated, filtered tool set.
When should I use MCP Funnel?
Use it when you are composing or cleaning up your MCP stack—after adding new servers but before you finalize agent prompts that depend on specific tools.
How do I add MCP Funnel to my agent?
Add a stdio MCP entry that runs `npx -y mcp-funnel` with an optional path to `.mcp-funnel.json`, or set `MCP_FUNNEL_CONFIG` to that file path.