Mcp Funnel

io.github.chris-schraPublished by GitHub account chris-schrav0.0.7Updated Oct 24, 2026

MCP proxy that aggregates multiple servers with tool filtering and customization

VerifiedSTDIODesktop onlyDeveloper Tools

Server details

Identifier: io.github.chris-schra/mcp-funnel
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account chris-schra for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.chris-schra%2Fmcp-funnel.svg)](https://sourceweft.com/mcp/io.github.chris-schra%2Fmcp-funnel?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP proxy that aggregates several MCP servers behind one endpoint, with tool filtering and customization.

What you can do: Aggregate multiple MCP servers behind a single proxy connection
Filter which tools from the underlying servers are exposed
Customize the aggregated tool set before it reaches the assistant
Configured through a config file, whose path can also be set by environment variable
When to use it: Useful when you already run several MCP servers and want one consolidated connection with a curated, filtered tool list instead of wiring each server separately.
Requirements: Runs locally over stdio via npx from the npm package mcp-funnel, so Node.js and network access for the package are needed. A configuration file describing the aggregated servers is required; its path can be given through the MCP_FUNNEL_CONFIG environment variable. Desktop client only.

Before you install

The proxy sits in front of other MCP servers, so the tools it exposes inherit their permissions and side effects; review the config to know which servers and tools are enabled. No authentication is declared.

Installation

In SourceWeft

Open Mcp Funnel in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.0.7LatestSep 16, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts