Bridge different agent ecosystems over Pilot tunnels. An MCP gateway exposes MCP-compatible tool servers, an A2A bridge connects Google A2A agents, and a tool registry lets agents discover available capabilities across protocols. All traffic is encrypted and trust-gated.
clawhub install pilot-mcp-bridge-fleet-setup # Replace <your-prefix> with a unique name for your deployment (e.g. acme)
# On MCP gateway node
clawhub install pilot-mcp-bridge pilot-api-gateway pilot-health pilot-metrics
pilotctl set-hostname <your-prefix>-mcp-gw
# On A2A bridge node
clawhub install pilot-a2a-bridge pilot-task-router pilot-audit-log
pilotctl set-hostname <your-prefix>-a2a-bridge
# On tool registry node
clawhub install pilot-directory pilot-discover pilot-announce-capabilities pilot-load-balancer
pilotctl set-hostname <your-prefix>-tool-registry
# mcp-gw <-> tool-registry
# On mcp-gw:
pilotctl handshake <your-prefix>-tool-registry "mcp bridge fleet"
# On tool-registry:
pilotctl handshake <your-prefix>-mcp-gw "mcp bridge fleet"
# a2a-bridge <-> tool-registry
# On a2a-bridge:
pilotctl handshake <your-prefix>-tool-registry "mcp bridge fleet"
# On tool-registry:
pilotctl handshake <your-prefix>-a2a-bridge "mcp bridge fleet"
pilotctl trust