For · MCP

Give your MCP servers a network.

MCP gives agents tools. Pilot gives agents each other. Connect MCP servers across machines, NATs, and clouds - no public IPs, no firewall tickets, no message broker.

Install in one line → Read the integration guide

The gap

MCP handles vertical. Pilot handles horizontal.

MCP · tool-calling

Agents call tools exposed by a local server.

Single-machine scope by default.

No peer discovery.

Great vertical: one agent, many tools.

Pilot · peer routing

Agents connect to each other across machines.

NAT-traversing encrypted tunnels.

Directory + trust + addressing built in.

Horizontal: many agents, one network.

What you can build

MCP servers, networked.

Remote MCP servers

Run heavy MCP tools on a dedicated box and connect to them from any agent, anywhere. No ngrok. No reverse tunnel gymnastics.

Shared fleet tooling

One MCP server serves dozens of agents across your org. Policy and trust enforced at the network layer, not in the tool.

Cross-org MCP federation

Expose an MCP server to a partner under explicit trust rules. Revocable, auditable, never public.

GPU-bound tools on demand

Keep the vector store, embeddings, and code-exec on the GPU box. Agents on laptops connect as if it were local.

Home-lab agents that reach out

Behind a double NAT. Still reachable. Dial out, get an address, stay online.

Multi-region MCP

Same MCP API, deployed in three regions. Agents route to whichever is reachable and fastest.

Up and running

Three steps.
Thirty seconds.

mcp-host ~ expose MCP server over pilot

0.8s

# on the MCP server host

$ curl -fsSL https://pilotprotocol.network/install.sh | sh

$ pilotctl daemon start --hostname mcp-host

Daemon running (pid 24817)

Address: 0:A91F.0000.7C2E

# your MCP server is already listening on :8080

$ sudo pilotctl gateway start --ports 8080 self

✓ gateway running · port 8080 → 0:A91F.0000.7C2E

# on the client agent

$ pilotctl handshake mcp-host

$ sudo pilotctl gateway start --ports 8080 mcp-host

✓ localhost:8080 → mcp-host (encrypted)

No reverse proxy. No tunnel broker. Your MCP server runs unchanged on one side, localhost on the other.

01
Install Pilot
One command on each host. The daemon registers and gets an address.
02
Expose your MCP port
sudo pilotctl gateway start --ports 8080 self - your existing MCP server is now reachable over the overlay.
03
Map on the client
Handshake, then map mcp-host:8080 to localhost. Any MCP client calls it as if local.