io.github.chris-schra/mcp-funnel MCP Server
io.github.chris-schra/mcp-funnel
MCP proxy that aggregates multiple servers with tool filtering and customization
What this kind of tool is for
- Automate a build, test, or deployment step you repeat by hand.
- Review or refactor code in an existing repository without leaving your agent.
- Bridge an internal service or CLI into the agent toolset.
How to compare servers like this
- Scope of control:
- Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
- Environment fit:
- Match the runtime it expects (Node, Python, a container) to what you actually run.
- Maintenance signal:
- Check the last-commit date — dev tooling that lags upstream breaks first.
- Config surface:
- Prefer tools whose environment-variable or config keys are documented plainly.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the io.github.chris-schra/mcp-funnel MCP server?
The mcp-funnel MCP server is a proxy that aggregates multiple MCP servers into a single interface, allowing you to filter and customize which tools are exposed. It enables centralized management of tool availability across multiple backend servers.
mcp-funnel acts as a middleware layer between your AI client and multiple MCP servers. It lets you combine tools from different servers, selectively expose or hide specific tools, and customize how they're presented—useful for managing complexity when working with many servers or controlling what capabilities are available in different contexts.
How to install io.github.chris-schra/mcp-funnel
Copy-paste configuration for popular MCP clients.
MCP_FUNNEL_CONFIGAlternative way to specify config file path
{
"mcpServers": {
"mcp-funnel": {
"command": "npx",
"args": [
"-y",
"mcp-funnel",
"-y",
"config_path"
],
"env": {
"MCP_FUNNEL_CONFIG": "<YOUR_MCP_FUNNEL_CONFIG>"
}
}
}
}Use cases
- Aggregate tools from multiple MCP servers into a single unified interface
- Filter and selectively expose tools based on your needs or security requirements
- Customize tool names and descriptions for different use cases or users
- Manage which tools are available in different client contexts
- Reduce complexity by hiding unnecessary tools from specific workflows
io.github.chris-schra/mcp-funnel MCP server FAQ
mcp-funnel is an MCP proxy server that sits between your AI client and multiple backend MCP servers, allowing you to aggregate, filter, and customize the tools exposed from those servers.
Install via npm with: npm install mcp-funnel
Yes, mcp-funnel is open source and available on GitHub at https://github.com/chris-schra/mcp-funnel.
mcp-funnel acts as a proxy that connects to multiple backend MCP servers. Refer to the repository documentation for configuration details on specifying which servers to aggregate.
Yes, mcp-funnel's core feature is tool filtering and customization, allowing you to selectively expose or hide tools from the aggregated servers.
Configure mcp-funnel as an MCP server in your client's settings, pointing it to your backend servers. It will then expose the filtered and customized tool set to Claude or Cursor.
README (reference)
Source of truth, from the repository.
../../README.md
Related MCP servers
App Store Connect MCP: apps, TestFlight, reviews, sales reports, and team users.

Serves a directory of Agent Skills over MCP: list, load, read files, run declared scripts

C64 Bridge
AI command bridge for Commodore 64 hardware and VICE emulator control.
WPF development knowledge and tooling for Claude Code, integrated with .NET SDK and language server support.
io.github.chrisbusbin-pixel/applianceiq
Home appliance MCP: CPSC recall lookup, lifespan, maintenance, repair-or-replace, energy cost.
io.github.chrisbusbin-pixel/debtfree
Debt payoff calculator: snowball vs avalanche, minimum payment trap, extra-payment impact.
