# ToolFunnel [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://github.com/Rendeverance/toolfunnel  
**GitHub Stars:** 39  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/toolfunnel

## Description
A zero-dependency MCP and Local tool gateway to host, forward, curate, and gate tools from MCP servers, reducing token costs and enabling policy control. Easily create and wrap MCP servers with zero code, supporting multiple protocol eras.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "toolfunnel": {
    "command": "npx",
    "args": ["-y","toolfunnel"]
  }
}
```

## Documentation

## What ToolFunnel does

ToolFunnel places one MCP gateway between an agent and locally hosted or upstream tools. It can serve tools defined in a JSON register, forward selected tools from attached MCP servers, and expose both through a single MCP endpoint. Seven demonstration tools are included, and ordinary scripts can be assembled into a packaged MCP server without writing an SDK-based server.

Its lean register gives agents brief descriptions first. Full tool instructions are fetched only when needed, which helps reduce the amount of tool schema text sent on each turn. Upstream tools can be curated, enabled or disabled, and promoted to a top-level set for frequent use.

A server-side policy gate runs PreToolUse and PostToolUse hooks around execution paths handled by the gateway. Decisions fail closed, allowing the same policy behavior to travel with the gateway instead of depending on a particular client. Optional JSONL auditing records tool runs, allow or deny decisions, and upstream connection changes.

## How it works

Tools and upstream MCP servers can be managed from plain JSON files, an optional loopback web interface, or eleven in-band functions named with the `tf_` prefix. These changes apply to a running gateway without a restart, so tools and attached servers can be selected during an active session. If an attached MCP process exits, ToolFunnel detects the failure and attempts background reconnection with backoff.

The `tf_pack` function packages a configured gateway as an npm package that can be installed with `npx`. Meta-tools can be disabled when the resulting package should present only the selected tools as an MCP server.

ToolFunnel also supports a transparent wrapper mode for one attached MCP server. The `toolfunnel wrap <server>` command makes the gateway translate between the legacy and modern MCP protocol styles. The wrapped side retains the upstream server's identity, tool names, results, errors, and notifications rather than receiving a ToolFunnel-specific prefix. Wrapping can persist across restarts, and the command supports `--off` and `--as` options.

The bridge handles the protocol-era differences described by the project, including progress tokens, cancellation translation on stdio, and selected elicitation and resource-subscription behavior. It can reconnect a wrapped server and re-establish subscriptions from a legacy server; subscriptions from a modern server are not relayed in the same way.

## Setup and configuration

ToolFunnel is configured around a tool register and attached upstream definitions. Use JSON files for repeatable configuration, the loopback web UI for interactive management, or the `tf_` functions when the gateway is already connected to an agent. A typical workflow is to register local scripts, attach an MCP server, curate which tools are visible, and optionally add policy hooks.

To inspect wrapping state, run `toolfunnel wrap` without a server name. Use `toolfunnel wrap --off` to return to the normal ToolFunnel surface, or provide `--as <name>` to choose the wrapped presentation name. The command probes the target protocol and reports a security notice when the server requires paths outside the gateway root.

## Limitations and notes

The audit log is disabled by default and must be enabled when required. ToolFunnel's wrapping support is designed around the protocol-era transition described by the project; legacy-to-legacy relay for elicitation is on the roadmap, and modern-server resource subscriptions are not yet relayed. Servers that need filesystem paths outside the gateway root require attention to the security notice shown during wrapping.

_Full upstream README: https://allmcps.com/mcp/toolfunnel/readme_

