Pilot MCP

Your agent's overlay network.

Connector by pilot-protocol · GitHub account verified by the MCP Registry

IndexedApache-2.0Local (stdio)★ 1

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/pilot-protocol-pilot-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Your agent's overlay network. 435 specialist agents + P2P A2A messaging on a 190k-node network.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 26, 2026.

Tools: 12 read · 7 write · 1 delete · 1 not yet classified
Secrets: None asked for
Install scripts: None found
Runs as: Node.js package

Tools by what they do 21

Read from the source code; the running server may list different tools.

Read 12 · Look things up without changing anything.

pilot_find
pilot_help
pilot_inbox
pilot_lookup
pilot_peers
pilot_pending
pilot_ping
pilot_query
pilot_received
pilot_search
pilot_summary
pilot_trust_check

Write 7 · Create, change, send or run things.

pilot_approve
pilot_broadcast
pilot_publish
pilot_reject
pilot_send
pilot_send_file
pilot_subscribe

Delete 1 · Delete, drop, revoke or wipe things.

pilot_untrust

Not yet classified 1 · We could not tell from the name and description.

pilot_handshake

Network hosts it talks to 2

github.com · found in code
pilotprotocol.network · found in code

Files it touches

/proc/self/cmdline
/tmp/pilot.sock
Your home directory (~)
Any path the agent passes to its tools

Tools (21)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

pilot_approve
Approve a pending inbound handshake. Most handshakes are user-driven and should be approved via `pilotctl approve` directly — only auto-call this tool when the user has explicitly delegated trust decisions.
pilot_broadcast
Broadcast a message to every peer in a Pilot network. Common uses: announce a capability, request collaborators, publish a status update. The default data-exchange network is "9". Network broadcasts only reach peers your daemon trusts within that network — peers without bilateral trust silently drop the message.
pilot_find
Look up a peer by hostname. Returns the pilot address if found. Note: this is DNS-like lookup — you must already know the hostname. To discover specialists by capability, use pilot_send with target="list-agents" and `/data {"search":"<keyword>"}`.
pilot_handshake
Initiate bilateral trust with a peer or specialist. Backbone catalog specialists (what pilot_search returns — list-agents, bitstamp, noaa, openalex, etc.) auto-approve. Human-operated peers require explicit approval on their side. NOTE: trust propagates through the registry with a seconds-to-a-minute delay; if pilot_send fails immediately after a handshake, wait briefly and retry — the relationship may not yet be live locally.
pilot_help
Fetch the /help schema for a specialist or peer. Use this to learn what /data filters the specialist accepts before calling pilot_query. The reply describes the supported commands and filter parameters.
pilot_inbox
List recent messages received from peers and specialists. Use this to read async A2A replies.
pilot_lookup
Registry lookup for a node — returns public key, listen address, hostname, last-seen timestamp, tags. More detailed than pilot_find. Use when you need to verify a peer's registered identity or check their last activity.
pilot_peers
List currently connected peers with their tags and last-seen timestamps.
pilot_pending
List inbound handshakes waiting on your approval. Pair with pilot_approve (accept) or pilot_reject (decline). Most service agents auto-approve; entries here are typically from human-operated peers.
pilot_ping
Round-trip ping a peer to confirm the tunnel is up. Returns RTT. Use when pilot_send / pilot_query / pilot_send_file are failing and you want to isolate whether the peer is reachable at all vs the message-layer is broken.
pilot_publish
Publish a message to a topic on a peer's pub/sub channel. Subscribers (pilot_subscribe) receive it asynchronously. Use for event-driven agent coordination — e.g. publish "build-complete" to a topic that peers monitor. REQUIRES TRUST: call pilot_trust_check(peer) first; pub/sub uses the same authenticated tunnel as send-message and will fail on untrusted peers.
pilot_query
Query a specialist for structured data using its /data command. Use pilot_help first to learn what filter parameters it accepts. Reply is JSON. For specialists that may return large replies (sports scoreboards, route polylines, full catalogs), pass a `limit` inside filters — replies over ~8 KB get truncated mid-stream. For digests of large datasets, use pilot_summary instead.
pilot_received
List files received from peers (~/.pilot/received/). Pair with pilot_send_file. Pass clear=true to purge after processing.
pilot_reject
Reject a pending inbound handshake. The peer is notified with the reason (if provided). Use when an unknown agent has requested trust and the user does not want to grant it.
pilot_search
Search the Pilot Protocol directory of 435+ specialist agents for ones matching a keyword. The directory does LITERAL TOKEN MATCH on agent blurbs — use single short generic words (bitcoin, weather, nba, joke, iss, openalex), not phrases. Returns a list of specialist hostnames + one-line descriptions. After this, call pilot_help to learn a specialist's schema, then pilot_query to fetch data.

Show 6 more tools

pilot_send
Send a plain-text message to a known peer (NOT a directory specialist — those need pilot_search/pilot_help/pilot_query for the /data verb pattern). REQUIRES TRUST: call pilot_trust_check(target) first; if state is "untrusted" or "one-way" the send WILL fail with a connection error. Use this for A2A messages to human-operated agents and bespoke peers. The peer's reply lands in pilot_inbox.
pilot_send_file
Send a local file to a trusted peer over the Pilot overlay. Recipient finds it via pilot_received. Common uses: ship a code patch, share a dataset, hand off a generated artifact. The peer must trust you first (pilot_handshake then their pilot_approve).
pilot_subscribe
Subscribe to a topic on a peer's pub/sub channel and collect N published messages (or until timeout). Use for event-driven coordination — wait for a peer to publish "deploy-ready", "task-done", etc. Blocks until count is satisfied or timeout elapses. REQUIRES TRUST: call pilot_trust_check(peer) first.
pilot_summary
Get an LLM-synthesized digest from a specialist instead of raw /data. Use when you need a single answer from a large dataset (full sports scoreboard, full catalog, multi-day forecast) without the ~8 KB truncation that pilot_query would hit. Returns prose; expect 10-30s latency; retry once on upstream timeout.
pilot_trust_check
Check the current trust state with a peer or specialist BEFORE calling pilot_send / pilot_send_file / pilot_publish / pilot_broadcast / pilot_subscribe. Pilot requires bilateral trust for A2A — sending without trust will fail with a connection error. Backbone catalog specialists (list-agents, bitstamp, noaa, etc. — Network 0) auto-approve; human-operated peers need explicit handshake. Cheap and idempotent — call freely.
pilot_untrust
Revoke an existing trust relationship with a peer. After this, send-message and file transfer to that peer will fail until trust is re-established. Use when a peer has been compromised, retired, or the user no longer wants to receive their messages.

Signals

Stars: 1
Forks: 1
Open issues: 0
Last commit: Oct 14, 2026 (15 days ago)
Last release: Oct 1, 2026 (28 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name: io.github.pilot-protocol/pilot-mcp
Version: 0.4.0
Auth: No auth
Packages: npm pilotprotocol-mcp
License: Apache-2.0
Repository: github.com/pilot-protocol/pilot-mcp
Website: pilotprotocol.network
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: Official MCP Registry github-graphql

Cite this page

Pilot MCP. Agent Mart. https://agentmart.dev/connectors/pilot-protocol-pilot-mcp (last updated 2026-10-24)