What problem does it solve? Connecting multiple MCP servers to the Pi coding agent normally floods the context window with hundreds of tool definitions, often 10k+ tokens per server. This Skill replaces that with one ~200 token proxy tool that discovers and calls MCP capabilities on demand, keeping the agent's context clean. ## Core Features & Use Cases - Proxy Tool Mode: Search, describe, list, and execute MCP tools through a single mcp proxy instead of registering every tool individually. - Direct Tool Registration: Promote 5-20 high-priority tools to first-class agent tools, with per-server or global defaults and exclusion lists. - Lifecycle & OAuth Management: Configure lazy, eager, or keep-alive server lifecycles with idle timeouts, plus automated OAuth flows for authenticated servers. - Use Case: A developer connects chrome-devtools, GitHub, and Postgres MCP servers to Pi, registers only screenshot and issue-creation tools directly, and lets everything else lazy-load through the proxy, avoiding context bloat. ## Quick Start Install the adapter with 'pi install npm:pi-mcp-adapter', then ask the agent to create a .mcp.json configuring your MCP servers and search for available tools through the mcp proxy.