Best for
- Pi coding-agent users who want lower MCP context overhead
- Developers who need access to multiple MCP ecosystem services
- Users who want lazy connections, metadata caching, or optional direct tool registration
P
61FMRS · C
This project is a Pi-focused MCP adapter extension rather than a standalone domain-specific MCP server. Its main value is reducing context usage through one proxy tool, lazy startup, and metadata caching; actual capabilities, permissions, and risks depend on the MCP servers configured by the user.
Pi MCP Adapter is a Pi coding-agent extension that exposes configured MCP services through one proxy tool for on-demand discovery and invocation. It starts servers lazily by default, caches tool metadata, and supports stdio, Streamable HTTP, and SSE fallback to reduce context-window usage.
Tools
mcp
Searches, lists, describes, connects to, and calls tools from configured MCP servers; it also exposes server instructions, UI messages, and OAuth actions.
Setup
Run pi install npm:pi-mcp-adapter, then restart Pi. Put project configuration in .mcp.json or shared user configuration in ~/.config/mcp/mcp.json. You can also run pi-mcp-adapter init to scan host-specific configurations.
claude_desktop_config.json
{"mcpServers":{"chrome-devtools":{"command":"npx","args":["-y","chrome-devtools-mcp@latest"]}}}
Fit and risk
Not for
- Users who do not use Pi
- Workflows requiring server-process sharing across Pi sessions
- MCP sampling workflows requiring context inclusion, tools, stop sequences, audio, or image content
Required permissions
- Read and write Pi MCP configuration, tool metadata caches, and OAuth credential directories
- Start configured local MCP processes and access their working directories
- Access configured HTTP MCP endpoints, headers, environment variables, and OAuth credentials
- Depending on the configured MCP servers, access files, browsers, databases, APIs, or other external resources
Risks and side effects
- Configured MCP servers may receive the file, network, database, or API access required by their configuration and use
- OAuth authorization URLs, codes, and tokens are sensitive credentials
- Oversized text results may be written to the system temporary directory and are not cleaned up automatically
- Review imported host configurations and their permission scope before relying on them
Troubleshooting
- Restart Pi after installation
- Check the precedence of .mcp.json, ~/.config/mcp/mcp.json, the Pi global override, and .pi/mcp.json
- Run /mcp to inspect server status, tools, and configuration; use /mcp reconnect <server> when needed
- Run /mcp setup or pi-mcp-adapter init when standard configuration files are absent
- For remote OAuth, use auth-start to obtain the URL and auth-complete with the full redirect URL or code
- After first enabling directTools, verify the metadata cache; use /mcp reconnect <server> if necessary
Use cases
Using database, browser, and API MCP services from Pi on demand
Discovering MCP tools through search and description
Promoting a selected set of tools with directTools
Completing OAuth flows in remote or headless environments
Supported clients
PiFull support