PMCP - Progressive MCP
Progressive disclosure for MCP - Minimal context bloat with on-demand tool discovery and dynamic server provisioning.
The Problem
When Claude Code connects directly to multiple MCP servers (GitHub, Jira, DB, etc.), it loads all tool schemas into context. This causes:
- Context bloat: Dozens of tool definitions consume tokens before you even ask a question
- Static configuration: Requires Claude Code restart to see new servers
- No progressive disclosure: Full schemas shown even when not needed
Anthropic has highlighted context bloat as a key challenge with MCP tooling.
The Solution
PMCP acts as a single MCP server that Claude Code connects to. Instead of exposing all downstream tools, it provides:
- 26 stable meta-tools (not the 50+ underlying tools)
- Lazy by default: downstream servers are available on demand and only eager-start when listed in
autoStart - Dynamically provisions new servers on-demand from a manifest of 90+
- Progressive disclosure: Compact capability cards first, detailed schemas only on request
- Policy enforcement: Output size caps and optional secret redaction
