ゼロ依存性MCPとローカルツールゲートウェイ:他のMCPサーバーから任意の言語で独自のツールをホストし、転送し、ツールをキュレーションし、エージェントトークンのコストを削減し、実行前に、独自のポリシーのホックを介してすべての呼び出しをゲートし、ゼロコードで簡単に独自のMCPサーバーを作成 - そしてすべてのMCPサーバーをラップして、両方のプロトコルの時代、目に見えないを話す。

ゼロコード、ゼロ依存関係:60秒で独自のMCPサーバー - 3つの普通のスクリプトから名前付け、パッケージ化、ポリシー指定のMCPサーバー(画面上のすべての出力は実際の出力です。デモを参照してください)

** 447 完全なドキュメント: ToolFunnel User Manual** - インストール、Web UI、書き込みツール、MCP サーバー、ポリシーゲート、パッケージ、トラブルシューティング、スクリーンショットと作業例で説明されているすべて。 このREADMEは概要です。マニュアルは参考です。

問題

Toolfunnelは、複数の問題を1つのパッケージで解決するように設計されています。

モデルコンテクストプロトコル(MCP)は、AIエージェントが多くのサーバーからツールを呼び出すことができます。 しかし、すべての接続されたサーバーは、ツールスキーマのallをすべてのターン上のモデルのコンテキストにダンプします.

ToolFunnel

A zero-dependency MCP and Local tool gateway: host your own tools in any language, forward and curate tools from other MCP servers, expose them leanly to cut agent token cost, gate every call through your own policy hooks before it runs, create your own MCP servers easily with zero code - and wrap any MCP server so it speaks both protocol eras, invisibly.

Zero code, zero dependencies: your own MCP server in 60 seconds - from three ordinary scripts to a named, packaged, policy-gated MCP server (everything on screen is real output; see demo/):

📖 Full documentation: the ToolFunnel User Manual - installation, the web UI, writing tools, attaching MCP servers, the policy gate, packaging, and troubleshooting, all illustrated with screenshots and worked examples. This README is the overview; the manual is the reference.

The problem

Toolfunnel is designed to solve multiple issues in one package :)

The Model Context Protocol (MCP) lets an AI agent call tools from many servers. But every connected server dumps all of its tool schemas into the model’s context on every turn. Connect a handful of rich MCP servers and you’ve spent thousands of tokens describing tools the agent won’t use this turn - slower, costlier, noisier.

Similarly, working with AI I found myself generating many many tools, some of which I wanted to use with different AI workflows, some I didn’t, and I didn’t want to keep setting them up, I also didn’t wish to keep many different setups for different workflows. Therefore ToolFunnel was born so that all of my multi-use tools and common MCP servers can be in one place, with any workflow, and I can easily select which I want to use with whatever workflow and even change or add tools during a session with simple toggles in the UI. I also wanted to wire up and test MCPs live, in the running session, without resetting the CLI or restarting anything - and have their tools show up in the tools list straight away; ToolFunnel does exactly that.

Often also, there’s also no consistent way to govern what an agent may run: hooks and policies live in the host (a specific CLI or otherwise), so they don’t travel when you switch clients - with ToolFunnel, this is easy because your hooks travel with the tools - it can become your one swiss-army knife for many different workflows.