Cette page est affichée en anglais. Une traduction française est en cours.
MCP ConfigsMay 14, 2026·2 min de lecture
pi-mcp-adapter — One Proxy Tool for MCP (Pi)
pi-mcp-adapter lets Pi use MCP servers without loading hundreds of tool defs; verified 666★ and pushed 2026-05-13.
Prêt pour agents
Staging sûr pour cet actif
Cet actif est d'abord staged. Le prompt copié demande à l'agent d'inspecter les fichiers staged avant d'activer scripts, config MCP ou config globale.
Stage only · 17/100Policy : staging
Surface agent
Tout agent MCP/CLI
Confiance
Confiance : Established
Commande de staging sûr
npx -y tokrepo@latest install 023264bf-a70f-5d9b-bf4a-6211a7a04c04 --target codexStage les fichiers d'abord; l'activation exige la revue du README et du plan staged.
Introduction
pi-mcp-adapter lets Pi use MCP servers without loading hundreds of tool defs; verified 666★ and pushed 2026-05-13.
Best for: Agent users who want MCP capabilities but need to keep context windows small and lazy-load tools
Works with: Pi agent, shared MCP config files (.mcp.json, ~/.config/mcp/mcp.json), and MCP servers runnable via npx/uvx/docker
Setup time: 6-15 minutes
Key facts (verified)
- GitHub: 666 stars · 118 forks · pushed 2026-05-13.
- License: MIT · owner avatar + repo URL verified via GitHub API.
- README-backed entrypoint:
pi install npm:pi-mcp-adapter.
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.json and ~/.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 directTools setting to register individual tools when you want less indirection.
Source-backed notes
- README install command is
pi install npm:pi-mcp-adapter and suggests restarting Pi afterward.
- README provides a minimal
.mcp.json snippet with an npx server and shows proxy calls like mcp({ 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 setup when 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
directTools when you prefer individual tool registration over a single proxy tool.
Fil de discussion
Connectez-vous pour rejoindre la discussion.
Aucun commentaire pour l'instant. Soyez le premier à partager votre avis.