pi-mcp-adapter
Pi MCP Adapter lets the Pi coding agent use MCP servers without filling its context window. The README's reasoning is that a single MCP server can burn 10k+ tokens on verbose tool definitions, and it cites a blog post arguing you might not need MCP at all. Rather than dropping the MCP ecosystem (databases, browsers, APIs), the adapter exposes one proxy tool of about 200 tokens and lets the agent search and discover tools on demand: `mcp({ search: "screenshot" })` finds a tool, and `mcp({ tool: "...", args: '{...}' })` calls it, which the README contrasts with 26 tools cluttering the context.
Install with `pi install npm:pi-mcp-adapter` and restart Pi. It reads standard MCP files automatically (`~/.config/mcp/mcp.json`, `.mcp.json`, plus Pi-specific override files), with a documented precedence order. Servers are lazy by default: they connect only when a tool is called, disconnect after an idle timeout (10 minutes by default) and use cached metadata so search works offline; `eager` and `keep-alive` modes are available, and `directTools` can promote chosen tools. The README also covers MCP UI integration. It is MIT licensed.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-18
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 30
- Latest release
- v5.3.2 (2026-10-17)
- Open issues
- 0
- Recent issues with at least one comment
- 6/16
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!