ToolFunnel logo

ToolFunnel

Routes, curates, governs, and wraps MCP and local tools through one zero-dependency gateway.

Install ToolFunnel

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "toolfunnel": {
      "command": "npx",
      "args": [
        "-y",
        "toolfunnel"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y toolfunnel

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked .

Overview

ToolFunnel is a zero-dependency MCP and local tool gateway for hosting scripts, forwarding tools from other MCP servers, and controlling execution through policy hooks. It presents short tool briefs to reduce context usage, then retrieves full instructions when needed. Configuration can be changed through JSON files, a loopback web UI, or in-band management functions while the gateway is running. Reach for ToolFunnel when you need a shared, client-independent tool registry, live upstream management, audit logs, or protocol translation between MCP generations.

Use cases

  • Host scripts as a packaged MCP server
  • Curate upstream MCP tools for different workflows
  • Apply execution policies across MCP clients
  • Reduce tool-schema context sent to agents
  • Wrap legacy MCP servers for newer clients

Key features

  • Hosts local tools from a JSON register
  • Forwards and curates upstream MCP servers
  • Uses on-demand tool instructions
  • Runs fail-closed pre- and post-use hooks
  • Supports live management and reconnects
  • Translates between MCP protocol eras

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

9/9 checks healthy over the last 98d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11h ago via OSV.dev · toolfunnel (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars39Stargazers on the source repository.
Last commit1d agoMost recent push to the default branch.
MaintenanceActively maintainedStatus declared by the project or listing owner.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How ToolFunnel works

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.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about ToolFunnel

ToolFunnel is an MCP server that connects agents to locally hosted tools and attached upstream MCP servers through one gateway. Its main tools support registration, curation, toggling, policy hooks, auditing, packaging, and protocol-era wrapping. It exposes lean tool briefs and fetches full instructions on demand.

Install and configure ToolFunnel using its command-line gateway, JSON registers, optional loopback web UI, or in-band `tf_` management functions. A configured server can also be packaged with `tf_pack` as an npm package installable with `npx`.

Run `toolfunnel wrap <server>` after attaching the upstream server. ToolFunnel probes the server, persists the wrapping choice, and translates between legacy and modern MCP protocol styles. Use `toolfunnel wrap --off` to disable wrapping or `--as <name>` to choose its presented name.

Yes, ToolFunnel reduces schema context by showing agents short tool briefs and retrieving full instructions only when a tool needs them. Upstream tools can also be curated or toggled so workflows expose only the tools they need.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewToolFunnel AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/toolfunnel?style=directory)](https://allmcps.com/mcp/toolfunnel)
HTML Embed
<a href="https://allmcps.com/mcp/toolfunnel"><img src="https://allmcps.com/api/badge/toolfunnel?style=directory" alt="ToolFunnel on AllMCPs" /></a>