mcp-lazy-proxy logo

mcp-lazy-proxy

Free

Lazy-load your MCP servers. Two meta-tools instead of hundreds of tool schemas — cut context bloat, keep every backend, load tools on demand or keep them eager

Visit Website
Related by shared tags and keywordssudonotestzc-versoespolls
ai-toolscontext-optimizationcontext-optimization-tooldeveloper-toolslocal-llmaiai assistantautomation

Overview

MCP Lazy Proxy is a lazy proxy for LLM clients that exposes only two meta-tools, get_mcp_tools and call_mcp_tool, instead of injecting every backend MCP server's tool schemas into the model context. Backend servers are connected lazily, their tool lists are cached, and idle connections are closed automatically. The proxy supports both remote (HTTP/Streamable) and local (stdio subprocess) MCP servers, and can run either as a stdio subprocess spawned by an MCP client or as a self-hosted HTTP server for shared use. It allows marking a backend as a favorite to inject its schemas eagerly while the rest stay lazy, providing a middle ground between all-lazy and all-eager approaches. The proxy also advertises the backend catalog via MCP instructions, so the model knows what's available up front.

Pricing

Free

Detailed plans have not been confirmed in our catalog. Check the official website for current limits and billing terms.

Visit Website

Prices and limits may change. Confirm the currency, billing period, seat minimum and usage caps on the official website.

Use Cases

  • Teams use MCP Lazy Proxy to reduce context bloat when connecting many MCP servers to a model.
  • Developers use MCP Lazy Proxy to run local models on resource-constrained hardware without context overflow.
  • Teams use MCP Lazy Proxy to share a single MCP configuration across multiple machines or agents via a self-hosted HTTP server.
  • Users use MCP Lazy Proxy to mark frequently used backends as favorites for faster direct tool calls.
  • Developers use MCP Lazy Proxy to discover and invoke tools from remote and local MCP servers on demand.
  • Teams use MCP Lazy Proxy to benchmark the tradeoff between context size and latency for different MCP configurations.

Features

Expose two default meta tools

Discover backend tools with filters

Forward backend tool calls unchanged

Cache discovered backend tool lists

Close idle connections automatically

Connect remote and local MCP servers

Load favorite backend schemas eagerly

Reviews

No reviews yet. Be the first to share your experience!