Repository navigation
Remote Client
Remote operator and remote agent onboarding direction. The product is single-host, but agents (Codex, Claude Code, custom MCP servers) routinely connect from other processes on the same machine — and occasionally over a tunnel from another host.
- Launch the orchestration server.
- Open the desktop shell, navigate to Providers.
- Use Auto-Connect with the appropriate credential.
- Assign roles (
planner,coder, etc.) — CLU routes from there.
- Stand up the MCP server on a loopback port.
- POST to
/api/runtime/mcp-serverswith the endpoint definition. - The runtime probes the endpoint asynchronously and exposes it through
/api/dashboard.
The admin API binds to 127.0.0.1:7300. To reach it from another host, use a trusted
transport — ssh -L 7300:127.0.0.1:7300 user@host is the canonical pattern. The product
intentionally does not expose the API on an external interface.
The Beacon module advertises the runtime on the local network for trusted clients.
Beacon state is exposed via /api/beacon.
See also: Auto-Connect AI · API Reference · Architecture
Source for this wiki is maintained under docs/wiki/ in the Master-Control-Orchestration-Server repository.
Setup
Connect Clients
Operate
- Daily Operations
- Dashboard
- Telemetry and Activity
- Gateway
- Worker Pools
- Sub-Agents
- Governance
- CLU Governance
- Privileges
Maintain
Troubleshoot
Reference