What problem does it solve? Agents loaded with too many MCP servers and tools become slower, more error-prone, and more likely to pick the wrong tool, because every tool description consumes context on every turn and raises cognitive load. ## Core Features & Use Cases - Minimal Tool Enablement: Enable only the MCP servers the current work actually uses and remove the rest, preferring official servers for credentialed tools. - MCPorter-Based Access: Route MCP access through MCPorter (search/describe/call with index exposure) instead of registering every server as native agent tools, with a canonical config at ~/.mcporter/mcporter.json shared across Pi, Cursor, and shell agents. - Guardrails for Write Access: Add logging hooks before enabling write-scoped servers, and never expose mega-servers like dockhand (300+ tools) natively. - Use Case: When an agent thrashes between tools or underperforms, trim its toolset to a few sharply-described tools rather than switching to a smarter model. ## Quick Start Review my agent's configured MCP servers and tools, then remove everything not needed for the current task and route the rest through MCPorter.