MCP Dev Summit Bengaluru 2026

Connect three MCP servers and 55,000 tokens are consumed before the agent reads the user's query. Perplexity's CTO called this out at Ask 2026. Cloudflare measured 244,000 tokens for their API surface. The protocol isn't the problem. The "load everything upfront" pattern is.

FastMCP Code Mode solves this server-side, but requires the server author to opt in. Most MCP servers in the wild will never add it.

I'm currently building mcp-guardian, an open-source Python proxy that addresses this for any server, unmodified. It will do two things:

1. Tool scoping: filter tools/list against a YAML config so agents only see allowed tools. delete_repo won't exist in the agent's world.

2. Progressive disclosure: expose three meta-tools (search_tools, get_schema, execute_tool) instead of full schemas. Agents will start at ~300 tokens instead of ~8,000 and load schemas on demand.

I'll live-demo: direct connection (14 tools, ~8,000 tokens) vs through the proxy (3 meta-tools, ~300 tokens). I'll walk through the JSON-RPC interception, share token benchmarks, and compare with Code Mode. They're complementary, not competing.

The project will be open source.