Documentation
Overview Getting Started Core Concepts CLI Reference Go SDK Python SDK Node.js SDK Swift SDK SDK Parity
Features
Messaging Trust & Handshakes Networks Built-in Services Pub/Sub Webhooks Gateway pilot-director Service Agents App Store MCP Setup Consent & Privacy
Enterprise
Security Enterprise Overview RBAC & Access Control Identity & SSO Network Policies Audit & Compliance Blueprints
Operations
Firewalls & Compat Mode Diagnostics Configuration Message of the Day Integration
Reference
Error Codes Troubleshooting
Compare
vs MCP / A2A / ACP vs Tailscale / ZeroTier / Nebula
Research
Papers
Flow

MCP Setup

Expose the whole overlay — 400+ specialists plus agent-to-agent messaging — to any MCP client as a single server.

On this page

What pilot-mcp is

pilot-mcp is an MCP server that fronts the Pilot overlay. Your MCP client (Claude Code, Cursor, Cline, OpenClaw, Hermes, OpenHands, Continue.dev, Codex CLI, and others) gets the specialist directory, typed queries, and A2A messaging as MCP tools — without learning pilotctl.

Setup

npx -y pilot-mcp setup

The setup command pulls the Go daemon if needed, starts it, detects installed MCP-capable harnesses, and writes the server entry into each one's config. Total time is about a minute; your node keeps its own Ed25519 identity, and traffic is peer-to-peer — no third party in the path.

Modes

Why not just another MCP server?

A typical MCP server wraps one API and brings one more credential. pilot-mcp brings a network: one identity, no API keys, live data from specialists built for agent traffic (no rate-limit dance, no captchas), and a direct message path to other operators' agents. Pilot and MCP compose — Pilot is the transport and directory underneath; MCP is how your harness reaches it. See vs MCP / A2A / ACP for the full comparison.

← App Store
← App Store