pilot-mcp-bridge

Expose Pilot Protocol daemon operations as MCP tools.

7|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-mcp-bridge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pilot-mcp-bridge
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-mcp-bridge
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-mcp-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MCP bridge exposes Pilot Protocol operations as MCP tools, enabling Claude Code/OpenClaw workflows to interact with the Pilot daemon.

Core Features & Use Cases

  • Expose key Pilot Protocol functions as MCP tools (daemon status, info, peers, etc).
  • Provide a bridge to integrate Pilot with Claude Code, OpenClaw, and MCP-based clients.
  • Use case: A developer wants to automate Pilot operations inside Claude Code/OpenClaw tasks via MCP.

Quick Start

Start the Pilot daemon and run the MCP bridge to expose Pilot tools to Claude Code/OpenClaw.

Frequently Asked Questions about pilot-mcp-bridge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I expose Pilot Protocol operations as MCP tools for Claude Code?

An MCP bridge exposes Pilot Protocol operations as tools by wrapping the Pilot daemon, enabling Claude Code workflows to interact with daemon features like status, info, and peers via MCP tooling.

What is needed to run a Pilot daemon MCP bridge?

Running a Pilot daemon MCP bridge requires an active Pilot Protocol environment with a running daemon, a valid path to pilotctl, and compatibility with MCP client tooling.

Can I automate Pilot daemon tasks inside OpenClaw workflows via MCP?

Yes, you can automate Pilot daemon tasks inside OpenClaw by applying an MCP server bridge that exposes Pilot Protocol functions as MCP tools, allowing agent workflows to access daemon features.

What Pilot Protocol functions can I access through an MCP server?

Through an MCP server, you can access key Pilot Protocol functions exposed as tools, including daemon status, daemon info, and peers, facilitating integration with MCP-based clients.

Does the Pilot MCP bridge require a running daemon to operate?

Yes, the Pilot MCP bridge requires a running Pilot daemon to operate, because it acts as a wrapper that exposes the daemon's operations as MCP tools for client integrations.