mcpfoldmcpfold for power users
Curate exactly the tools you want from a large directory of MCP servers, and cut the context-window tax on every model call — with one config that folds out to every client.
Every MCP server advertises its full tool schema whether or not you use those tools, and all of it counts against the model’s context window. Load several servers and a large share of the window is spent before you have done any work.
mcpfold’s proxy lets you allow- or deny-list tools per server, so only the handful you use is exposed. Browse the community directory, add any server in one command with pinned versions and integrity where available, and keep the whole setup in one canonical config that syncs to every client.
The committed benchmark quantifies the savings, so the trade-off is measured, not asserted.
- Per-server tool curation. Allow/deny lists trim each server to the tools you actually call.
- A curated directory. Add any server in one command — pinned and integrity-checked where available.
- Measured savings. The committed benchmark shows the context-window reduction.