MCP gives agents tools. Pilot gives agents each other. Connect MCP servers across machines, NATs, and clouds — no public IPs needed.
One binary. One command. Zero networking config. Your agents are connected in under 30 seconds.
Open source · AGPL-3.0 · GitHub →
# Install (30 seconds)
curl -fsSL https://pilotprotocol.network/install.sh | sh
# Your agent is on the network
pilotctl daemon start --hostname my-mcp-agent
# Send MCP results to a peer agent
pilotctl connect other-agent --message "query results"MCP connects agents to tools (databases, APIs, files). Pilot connects agents to each other. Neither replaces the other — together they make a complete agent.
| Capability | MCP | Pilot |
|---|---|---|
| Agent → Tool access | ✓ | — |
| Agent → Agent communication | — | ✓ |
| NAT traversal | — | ✓ |
| End-to-end encryption | — | ✓ |
| Peer discovery by hostname | — | ✓ |
| Works without public IP | — | ✓ |
No Docker. No Kubernetes. No YAML files. No networking configuration.
One command. Downloads a single binary (~10 MB), configures automatically. Works on Linux and macOS.
pilotctl daemon start --hostname my-agent
Your agent gets a permanent address and joins the network.
Dial any agent by hostname. Trust handshake, encryption, and NAT traversal happen automatically.
Real patterns for MCP-equipped agents that need to share data.
Single binary. Zero dependencies. Under 30 seconds.
curl -fsSL https://pilotprotocol.network/install.sh | sh Detects your platform, downloads a single binary (~10 MB), writes config, and starts the daemon.
Or with pip: pip install pilotprotocol · Python 3.10+
Set a hostname: curl ... | PILOT_HOSTNAME=my-agent sh
No. MCP handles tool access (databases, APIs, file systems). Pilot handles agent-to-agent communication. They are complementary — MCP is vertical (agent to tool), Pilot is horizontal (agent to agent). Use both.
Under 30 seconds. One command installs the binary, generates your identity, and starts the daemon. No configuration files to write, no ports to open, no cloud accounts to create.
No. Pilot handles NAT traversal automatically — STUN discovery, UDP hole-punching, and relay fallback. Your agents connect directly even behind corporate firewalls and carrier-grade NAT.
Yes, always. X25519 key exchange and AES-256-GCM encryption on every connection. Agents are private by default and require mutual trust establishment before any data flows.
The daemon is a single Go binary. Client libraries exist for Go (native) and Python (pip install pilotprotocol). The CLI works from any language that can shell out to pilotctl.
This page focuses on the practical networking problem: crossing NATs, no public IPs, zero config. The blog post covers the conceptual architecture of combining tools and network capabilities.
Want the full technical walkthrough? Read Connecting MCP Servers to Agents Across Any Network →