Mission Control

Use the provided install script to set up Mission Control locally or in Docker. The --local flag runs it as a Node.js process; --docker uses Docker Compose.

git clone https://github.com/builderz-labs/mission-control.git
cd mission-control
bash install.sh --local

For a containerized deployment with optional hardening (read-only root filesystem, non-root user, resource limits), use Docker Compose.

docker compose up
# Or with security hardening:
docker compose -f docker-compose.yml -f docker-compose.hardened.yml up -d

Open the browser and navigate to the setup wizard. Mission Control auto-generates the admin credentials and API key — note them from the terminal output or find them in Settings after login.

# Open: http://localhost:3000/setup
# Admin credentials are logged to stdout on first run

Set key environment variables before or after installation to connect Mission Control to your agent infrastructure. The most critical ones are listed below.

# In .env or docker-compose environment:
AUTH_USER=admin
AUTH_PASS=your-secure-password
OPENCLAW_STATE_DIR=/absolute/path/to/openclaw-state
MISSION_CONTROL_DATA_DIR=/data
MC_CLAUDE_HOME=/home/user/.claude

In the Mission Control dashboard under Agents, register your agent by selecting its framework type and providing the connection details. The dashboard will begin showing heartbeat status and task history immediately.

To let AI clients interact with Mission Control programmatically (dispatch tasks, read logs, check agent status), add it as an MCP server in your client configuration.

{
  "mcpServers": {
    "mission-control": {
      "command": "npx",
      "args": ["mission-control"],
      "env": {
        "API_KEY": "your-mission-control-api-key",
        "MC_BASE_URL": "http://localhost:3000"
      }
    }
  }
}