Skip to main content

Module mcp

Module mcp 

Source
Expand description

The fleet as an MCP server (#218).

prospero exposed REST + SSE only, so an agentic tool could not drive the fleet the way OpenClaw (openclaw mcp serve) and Vibe Kanban already allow. This is a thin adapter over the same FleetProvider seam the HTTP handlers use — no second control path, so both backends (LocalFleet, K8sFleet) work through it unchanged.

Auth. The transport is mounted inside the same router as the REST API, so the route_layer scope check runs first: /mcp requires operate (#2), the scope a spawn or kill needs. Read-only tools are reachable with that same credential rather than a lesser one — the surface is a driving surface, and splitting per-tool scopes here would put a second, divergent authorization model behind the one the route already enforces.

Structs§

AgentArgs
Arguments naming one agent.
EventsArgs
Arguments for reading an agent’s history.
FleetMcp
The MCP server over one fleet.
InputArgs
Arguments for sending input to an interactive agent.
SpawnArgs
Arguments for a spawn.

Functions§

service
Mount the MCP server as an axum service at /mcp (#218).