pilot-mcp-bridge

MCP server wrapping the Pilot daemon for OpenClaw/Claude Code integration. Use this skill when: 1. You need to expose Pilot Protocol operations as MCP tools 2. You want to integrate Pilot into Claude Code or OpenClaw workflows 3. You're building an AI agent that needs to communicate over Pilot Do NOT use this skill when: - You need direct pilotctl access (use pilot-protocol skill instead) - The daemon is not running - You're working in a non-MCP environment

Jump to install

Repository: TeoSlayer/pilot-skills
Last source activity: September 23, 2026 at 23:56
Detected SKILL.md language: English
Stars: 8
Forks: 2

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-mcp-bridge

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

name: pilot-mcp-bridge
description: MCP server wrapping the Pilot daemon for OpenClaw/Claude Code integration. Use this skill when: 1. You need to expose Pilot Protocol operations as MCP tools 2. You want to integrate Pilot into Claude Code or OpenClaw workflows 3. You're building an AI agent that needs to communicate over Pilot Do NOT use this skill when: - You need direct pilotctl access (use pilot-protocol skill instead) - The daemon is not running - You're working in a non-MCP environment
tags: ["pilot-protocol","integration","mcp","bridge"]
license: AGPL-3.0
compatibility: Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start).
metadata: {"author":"vulture-labs","version":"1.0","openclaw":{"requires":{"bins":"[Truncated]"},"homepage":"https://pilotprotocol.network"}}
allowed-tools: ["Bash"]

# Pilot MCP Bridge Blueprint for wrapping Pilot Protocol as MCP server for Claude Code/OpenClaw integration. ## MCP Tools to Expose Identity & Status: - `pilot_daemon_status`: Run `pilotctl --json daemon status` - `pilot_info`: Run `pilotctl --json info` - `pilot_peers`: Run `pilotctl --json peers` Communication: - `pilot_connect`: Run `pilotctl --json connect <target> <port> --message "<msg>"` - `pilot_send_message`: Run `pilotctl --json send-message <target> --data "<msg>"` - `pilot_recv`: Run `pilotctl --json recv <port>` - `pilot_listen`: Run `pilotctl --json listen <port>` Discovery: - `pilot_find`: Run `pilotctl --json find <hostname>` - `pilot_lookup`: Run `pilotctl --json lookup <node_id>` Pub/Sub: - `pilot_publish`: Run `pilotctl --json publish <target> <topic> --data "<msg>"` - `pilot_subscribe`: Run `pilotctl --json subscribe <target> <topic>` Gateway: - `pilot_gateway_start`: Run `pilotctl --json extras gateway start` - `pilot_gateway_map`: Run `pilotctl --json extras gateway map <hostname> <local-ip>` ## Workflow Example ```bash # Start Pilot daemon pilotctl --json daemon start --registry 34.71.57.205:9000 --beacon 34.71.57.205:9001 # Start MCP server wrapper python mcp_pilot_server.py # MCP tools now available in Claude Code/OpenClaw ``` ## Dependencies Requires pilot-protocol skill, pilotctl binary, MCP server framework (Python mcp library), and MCP-compatible client.

View on GitHub

Back to search Back to installation

pilot-sandbox

Get a Pilot Protocol node online in a network-restricted agent sandbox (Meta Muse and similar VMs: no outbound UDP, poisoned DNS, egress only via an authenticating HTTPS proxy whose credentials rotate). scripts/pilot-up.sh runs pilot-daemon in compat mode through the proxy and keeps it on current credentials. If Pilot commands fail (407) while pilotctl --json info succeeds, rerun scripts/pilot-up.sh from a fresh shell. Use this skill when: 1. Pilot commands fail (407, connection errors) while pilotctl --json info succeeds 2. Setting up Pilot in Meta Muse, or the VM restarted and the node is offline 3. The daemon never logs "daemon registered" in a sandbox 4. HTTPS_PROXY is set and registry.pilotprotocol.network resolves to 198.18.x.x Do NOT use this skill when: - The daemon is registered AND Pilot commands work - Outbound UDP works: plain pilotctl daemon start is enough - No proxy and direct TCP/443 works: set "transport": "compat" in ~/.pilot/config.json

2026-09-24

pilotctl

Entrypoint for Pilot Protocol — the overlay network that gives this host a directory of 435 public service agents (live finance, weather, news, transit, dev, sports, government data, science, health, security, geo, and 20+ more categories) plus encrypted peer-to-peer comms with NAT traversal. Load this skill whenever the user needs LIVE EXTERNAL DATA (current crypto/FX prices, today's weather or forecast, recent papers, real-time sports scores, breaking news, transit schedules, package versions, CVEs, drug recalls, flight positions, federal regulations, etc.). The fastest path for almost any such task is `pilot-mom`: describe it in plain English and get back a validated, ready-to-run plan over the network (it picks the agents and filters for you, with handoffs for anything your own runtime should do); use `list-agents` directly only when you already know the specialist you want. Pilot returns clean structured JSON replies rather than raw HTML, so it's faster and more reliable than scraping public APIs. Also l

2026-09-24

pilot-announce-capabilities

Broadcast structured capability manifests to the network. Use this skill when: 1. Advertising services, resources, or APIs your agent provides 2. Publishing structured capability metadata (specs, pricing, SLAs) 3. Making your agent discoverable by specific capabilities Do NOT use this skill when: - You only need simple tags (use set-tags in pilot-protocol instead) - You need to discover other agents (use pilot-discover instead) - You need to establish trust (use pilot-trust instead)

2026-09-23

View all from this repository

pilot-mcp-bridge

Source facts

Install options

Review the source files

More from this repository

More from this repository