Zero-dependency MCP 및 Local tool Gateway : 다른 MCP 서버의 모든 언어, 앞으로 및 curate 도구에 자신의 도구를 호스팅하여 에이전트 토큰 비용을 삭감하고, 실행하기 전에 자신의 정책 후크를 통해 모든 통화를 게이트에두고, 0 코드로 쉽게 자신의 MCP 서버를 만들 - 그리고 ** 모든 MCP 서버를 치료하기 때문에 두 프로토콜 시대, 보이지 않는 **.

Zero code, Zero Dependencies: your own MCP server in 60 seconds - 3개의 정규적인 스크립트에서 이름, 패키지, 정책 gated MCP 서버 (각각 화면에 실제 출력; 데모/ 참조):

** 전체 문서: ToolFunnel User Manual** - 설치, 웹 UI, 쓰기 도구, MCP 서버, 정책 게이트, 포장, 문제 해결, 모든 스크린 샷과 일한 예로 설명. 이 README는 개요입니다. 설명서는 참고 사항입니다.

문제

Toolfunnel는 하나의 패키지에 여러 문제를 해결하도록 설계되었습니다 :)

Model Context Protocol (MCP)은 많은 서버에서 AI 에이전트 통화 도구를 제공합니다. 그러나 모든 연결된 서버 덤프 ** 모든 턴에 모델의 컨텍스트로 도구 스키마 **.

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.