MCP server composition

graph_os.mcp_server owns the graph-os transport and composition boundary. The action implementations remain in the agent plane and epistemic-graph; graph-os registers them once and exposes the same core through MCP and REST.

1. LaunchThe graph-os command starts the single serving lifecycle.
2. ComposeThe server binds the shared tool and REST application runtime.
3. Connect authorityTyped agent-utilities services and epistemic-graph clients supply domain behavior.
4. Open the fleetLazy fleet meta-tools expose admitted connector services.
5. Host co-servicesAgent WebUI and messaging use the same composed process authority.

The serving lifecycle mints process authority, bootstraps the engine, installs the gateway application adapter, attaches the lazy fleet surface, starts the native WebUI host when configured, and then serves stdio or streamable-http. Optional WebUI imports remain lazy.

The fleet loader uses GraphOS's native multiplexer. Its EG-backed catalog read is capability-gated on the generated kind-only AgentComponent.Search client contract. When that authority is unavailable, catalog refresh fails closed; it does not substitute a static reader. See Capability status.