What problem does it solve?
Configuring and calling Model Context Protocol (MCP) servers inside the Pi agent workspace requires manual wiring; this Skill standardizes how MCP servers are declared in mcp.json and exposed to the agent through one proxied mcp tool.
Core Features & Use Cases
- Unified MCP proxy: Exposes all configured MCP servers through a single
mcp tool with search, describe, and call operations, keeping large tool sets out of the active context.
- Flexible configuration: Supports project-local config at
/workspace/.pi/mcp.json and global config at /config/.pi/agent/mcp.json, with lazy server lifecycle by default.
- Interactive management: Provides
/mcp, /mcp tools, /mcp reconnect, and /mcp-auth commands for inspecting and managing server connections.
- Use Case: Add a filesystem MCP server to your workspace config, then search for its tools with
mcp({ search: "read file" }) and invoke them without restarting your session setup from scratch.
Quick Start
Copy the starter mcp.json example into /workspace/.pi/mcp.json, define your MCP servers, then ask the agent to list available MCP tools using the mcp tool.