Pilot MCP

by pilot-protocol

Not rated
GitHub

About

An MCP server that connects AI agents to the Pilot Protocol overlay network — permanent addressing, encrypted tunnels, and service discovery for agents.

Details

Author
pilot-protocol
Categories
Developer Tools

Setup

Install Pilot MCP in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/pilot-protocol/pilot-mcp

Follow the installation instructions in the repository README, then restart your MCP client.

The npm package ispilotprotocol-mcp. Its historical executable name ispilot-mcp; the unrelated npm package namedpilot-mcpis not Pilot Protocol's adapter and is never installed by these instructions.

Your agent's overlay network — local or hosted, your choice.435 specialist agents + A2A messaging to a 190k-node P2P network, exposed as one MCP server.

# Local (full P2P, your own identity, no third party): npx -y pilotprotocol-mcp setup # Hosted (no install, SSH key = identity, persistent): claude mcp add pilot ssh://you@ssh.pilot.protocol.network # planned v0.2

Auto-detects Claude Code, Cursor, Cline, OpenClaw, Hermes, OpenHands, Continue.dev, Codex CLI, Junie, GitHub Copilot, PicoClaw. Configures each. Total time: under a minute.

We deliberately donotoffer ephemeral anonymous HTTP — 30-second identities can't propagate trust through the registry, so they can't do the A2A that's Pilot's reason to exist. For a "try a query" demo without committing, usepilotprotocol.network/try.

MCP gave your agenttools. Pilot gives your agentpeers— a directory of 435 specialist agents you can query without an API key, plus direct A2A messaging to other operators' agents.

Q: "What's the current Bitcoin price across major exchanges?" web_search: blog post from 2024, 429 from CoinGecko, captcha from Coinbase. pilot-mcp: queries bitstamp, coinbase, kraken specialists in parallel. Returns structured JSON in ~300ms. No keys, no captchas. Q: "What papers cite arXiv:2507.14263?" web_search: Google Scholar gated, semanticscholar.org rate-limited. pilot-mcp: queries openalex specialist, returns 47 citations with abstracts. Q: "Is there a CVE for openssl in the past week?" web_search: NVD HTML scrape, missing the latest entries. pilot-mcp: queries cve-feed specialist, returns last 7 days of openssl CVEs. Q: "What's the BVG U-Bahn departure from Alexanderplatz?" web_search: BVG.de is JS-rendered, scrape fails. pilot-mcp: queries bvg specialist, returns next 10 departures with platforms.

10 MCP tools— shaped around the actual 3-command pattern (/help,/data,/summary) enforced by pilotctl. Bare messages without a verb prefix are silently no-ops; the tool surface prevents that mistake.

- pilot_search(keyword, limit?)— find specialists by keyword (literal token match — use short generic words:bitcoin,weather,nba)
- pilot_help(agent)— learn a specialist's/datafilter schema
- pilot_query(agent, filters?)— fetch structured data; detects ~8 KB truncation and surfaces a hint
- pilot_summary(agent, question?)— LLM-synthesized digest when/datawould exceed truncation

- pilot_send(peer, message)— plain text to a human-operated peer
- pilot_inbox(limit?)— read received messages

- pilot_handshake(target, reason?)— bilateral trust (warns about ~60s registry propagation delay)
- pilot_find(hostname)— DNS-like lookup
- pilot_peers()— connected peers + PATH (direct vs relay)
- pilot_approve(target)— accept pending handshake

6 MCP resources:pilot://catalog(live directory snapshot),pilot://inbox,pilot://trust,pilot://peers,pilot://identity,pilot://daemon-health.

5 MCP prompts: 3-command-pattern, a2a-message, handshake-first-contact, troubleshoot (Flow 3 debug), readiness-check.

# Claude Code — user MCP lives in ~/.claude.json; hooks live in ~/.claude/settings.json claude mcp add --transport stdio pilot -- npx -y pilotprotocol-mcp # Cursor — add to ~/.cursor/mcp.json {"mcpServers":{"pilot":{"command":"npx","args":["-y", "pilotprotocol-mcp"]}}} # Cline — add the same JSON to ~/.cline/data/settings/cline_mcp_settings.json # Continue.dev — merge into ~/.continue/config.yaml name: My Continue Config version: 1.0.0 schema: v1 mcpServers: - name: Pilot command: npx args: ["-y", "pilotprotocol-mcp"] # OpenHands — add to ~/.openhands/mcp.json {"mcpServers":{"pilot":{"command":"npx","args":["-y","pilotprotocol-mcp"]}}} # Hermes — add to ~/.hermes/config.yaml mcp_servers: pilot: command: npx args: ["-y", "pilotprotocol-mcp"] # Codex CLI — add to ~/.codex/config.toml [mcp_servers.pilot] command = "npx" args = ["-y", "pilotprotocol-mcp"] # PicoClaw — add to ~/.picoclaw/config.json {"tools":{"mcp":{"enabled":true,"servers":{"pilot":{"enabled":true,"command":"npx","args":["-y", "pilotprotocol-mcp"]}}}}} # Copilot CLI — add standard MCP JSON to ~/.copilot/mcp-config.json # Junie CLI/IDE — add standard MCP JSON to ~/.junie/mcp/mcp.json # OpenClaw — setup installs and enables the Pilot Policy plugin openclaw plugins inspect pilot-policy --runtime --json

- All overlay traffic flowsP2P over encrypted UDP(AES-256-GCM, X25519 key exchange, Ed25519 identity).
- An unmanaged node does not upload tool calls and every installed policy hook is a zero-side-effect pass-through.
- Specialist queries route through the Pilot rendezvous server (NAT-traversal coordinator) but thepayload is end-to-end encrypted; the rendezvous can see who is talking to whom, not what.
- For LAN-only deployments, pointpilot-daemonat a private rendezvous and stay air-gapped.
- When a node is explicitly adopted into Pilot Management, its pre/post action envelopes—including tool inputs and results—are sent to the hosted federation control plane for policy evaluation, approvals, and audit. That managed path is opt-in and fail-closed for pre-action decisions.

- Pilot Protocol:https://pilotprotocol.network
- Docs:
https://pilotprotocol.network/docs
- IETF draft:
https://www.ietf.org/archive/id/draft-teodor-pilot-protocol-01.html
- Source:
https://github.com/pilot-protocol/pilot-mcp

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Create crafted UI components inspired by the best 21st.dev design engineers.

Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server

An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .

MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent

ALAPI MCP Tools,Call hundreds of API interfaces via MCP

AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform

MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.

APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.

One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.

Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.