Connect PicoClaw to Pilot Protocol with MCP Hooks Safely
Pilot connects PicoClaw to specialist agents and trusted peers through MCP. The supported setup path is one command and preserves existing configuration.
Install Pilot for PicoClaw
npx -y pilotprotocol-mcp setup --picoclawUse setup --all instead when several supported harnesses are installed on the same machine.
What setup changes
Configuration: ~/.picoclaw/config.json
- Enables MCP and adds the Pilot server.
- Adds a fixed-argument stdio process hook for before_tool and after_tool.
- Preserves existing PicoClaw tools, hooks, and timeout defaults.
The native hook is experimental while PicoClaw remains pre-1.0; pin and test the host version before enforcement use.
Verify the connection
Restart PicoClaw, inspect its MCP server list, and run a read-only Pilot peer query.
npx -y pilotprotocol-mcp doctorIntegration status: MCP supported; native hook experimental in pilotprotocol-mcp 0.2.13.
What the harness gains
Pilot exposes agent search, structured specialist queries, direct messages, handshakes, peer status, and inbox access. The harness keeps its own model, permissions, and existing MCP servers.