Context Proxy
Front your existing MCP servers with a proxy that lazy-loads tool schemas so agent context stays smaller and cheaper.
Overview
Context Proxy is a MCP server for the build phase that lazy-loads downstream MCP tool schemas to cut context token overhead by about 6–7x.
What is this MCP server?
- MCP proxy that defers loading full tool schemas until they are needed
- Documented ~6–7x reduction in context token overhead from eager schema loading
- Stdio npm package mcp-lazy-proxy version 0.2.0
- Works as a drop-in layer in front of other MCP servers you already run
- Claimed 6–7x cut in context token overhead vs eager schema load
- Package version 0.2.0
- npm identifier mcp-lazy-proxy
What problem does it solve?
Connecting many MCP servers blows up the system prompt with tool JSON and leaves too little context for actual implementation work.
Who is it for?
Builders running multiple MCP integrations who are context-starved and want middleware optimization without rewriting each server.
Skip if: Single-tool setups with negligible schema size or teams that cannot add an extra stdio hop in their MCP chain.
What do I get? / Deliverables
After routing your host through the proxy, tool schemas load when needed so sessions stay within token budgets with the same downstream servers.
- Proxy layer in the MCP chain with on-demand schema loading
- Lower upfront tool-definition token use (README cites ~6–7x)
Recommended MCP Servers
Journey fit
Token-heavy MCP tool lists become a problem while wiring many servers during build, before you ship and optimize production agent stacks. A context proxy is an integration-layer concern: it sits between the host and downstream MCP servers without replacing those servers.
How it compares
MCP integration proxy for token savings, not a standalone skill or replacement for your business-logic MCP servers.
Common Questions / FAQ
Who is Context Proxy for?
It is for developers who operate several MCP servers through one agent and need to reduce upfront tool-schema tokens.
When should I use Context Proxy?
Use it during build and integration when lazy-loading schemas would free context for code, tests, and long threads.
How do I add Context Proxy to my agent?
Install the npm stdio package mcp-lazy-proxy, point it at your downstream MCP servers per the GitHub repo, and register the proxy as the MCP entry your host connects to.