MCP Tools Directory
← Browse integrations

Developer tools

io.github.kira-autonoma/context-proxy

Free account · sign-in required

Contact io.github.kira-autonoma/context-proxy

Loading secure sign-in…

Tools for autonomous AI agents

About this integration

MCP proxy that lazy-loads tool schemas to cut context token overhead by 6-7x

Transport
stdio
Authentication
unknown
Initial setup
unknown
Runtime
unattended
Evidence
documented
Version
0.2.0
Package
mcp-lazy-proxy
Last compatibility test
Not independently tested

Connect your agent

mcp-lazy-proxy

Publisher documentation and manifest were reviewed; the proxy and upstream packages were not executed or independently security-audited. Upstream servers retain their own permissions and credentials, and response compression may omit data by design.

Capabilities: Proxy configured stdio MCP servers, Lazy-load and cache tool schemas, Compress large tool responses, Report documented schema-token metrics

Connected profiles

Additional details

Registry identifier

io.github.kira-autonoma/context-proxy

Source ↗ · Checked 2026-09-17
Published version

0.2.0

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Source artifact

mcp-lazy-proxy

Source ↗ · Checked 2026-09-19
Source manifest version

0.2.0

Source ↗ · Checked 2026-09-19
Unattended configuration

Publisher documents launching the proxy as the client's MCP server with a reusable configuration of upstream processes.

Source ↗ · Checked 2026-09-19
Authentication and prerequisites

The proxy has no single documented credential mechanism; authentication and setup depend on each configured upstream MCP server, so both remain unknown rather than being inferred.

Source ↗ · Checked 2026-09-19
Connection configuration

The MCP client launches mcp-lazy-proxy with a local JSON configuration; the proxy then starts configured upstream stdio commands.

Source ↗ · Checked 2026-09-19
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-19