Main
Context-saver design: README argues MCP tool definitions are verbose, so the adapter exposes one proxy tool and lazy-connects to servers.
Shared config support: README says it reads
.mcp.jsonand~/.config/mcp/mcp.json, plus Pi-owned override files with clear precedence.Lazy lifecycle: README notes servers are lazy by default and metadata is cached so search/list works without a live connection.
Direct tools option: README documents a
directToolssetting to register individual tools when you want less indirection.
Source-backed notes
- README install command is
pi install npm:pi-mcp-adapterand suggests restarting Pi afterward. - README provides a minimal
.mcp.jsonsnippet with annpxserver and shows proxy calls likemcp({ search: "screenshot" }). - README documents config precedence across shared MCP files and Pi-owned override files.
FAQ
- Does it work with Cursor/Claude Code configs?: README says it can import host-specific configs via
/mcp setupwhen shared MCP files are missing. - Will tools show up instantly?: Not all — README says servers are lazy by default and tools are discovered on demand.
- When should I use direct tools?: Use
directToolswhen you prefer individual tool registration over a single proxy tool.