BLACK LABEL / OPERATOR

CONNECTOR GUIDE

Run a mission. Inspect the result.

Black Label Operator connects Claude and other MCP clients to your isolated hosted workspace. Run a bounded Claude Code or Codex mission and retrieve its status, artifacts, and receipts.

Before connecting

Connect your client

  1. Open your AI client's custom connector settings and add https://operator.blacklabelbots.com/mcp.
  2. Complete Operator's sign-in and authorization flow. Review the requested permissions.
  3. Ask for your Operator status. Confirm the workspace and selected provider are ready.

The public website-information endpoint at /agent/mcp is a separate service. It searches and reads public pages; it does not run a mission or access your workspace.

Your first mission

  1. Choose a small task with a concrete artifact, such as “Create a README checklist for reviewing a small website's accessibility. Save it as Markdown.”
  2. Use operator_start with your objective, provider (claude or codex), and a unique idempotency_key. Reuse that key for the same request after an uncertain response.
  3. Keep the returned run ID. Inspect it with operator_get_run.
  4. List results with operator_list_artifacts. Use operator_get_artifact to obtain metadata and the authorized download path.
  5. Open and review the actual result before relying on it. A completed run is not a guarantee that the artifact meets your objective.

Tools and permissions

ToolsBehaviorPermission
Status, read run, list artifacts, read artifactRead your own account, mission, or artifact metadata.operator:read
Connect Codex, check CodexBegin or complete provider device authorization in your workspace.operator:run
Start missionReserves trial/subscription usage and runs the selected provider. The mission can create or change files and access external services within its authorized environment.operator:run
BillingReads plan information and available checkout or billing paths. Does not charge a payment.operator:billing

Hosted limits

Hosted missions currently run once through the selected provider. The installed local adaptive runtime is a separate capability. Hosted operator_adaptive_start, operator_adaptive_status, and operator_adaptive_cancel report that local boundary; they do not start, inspect, or cancel a local task.

The hosted input and approval boundary tools currently return run_not_waiting and approval_not_found. They do not deliver additional input or approve an action. Customer-supplied verification commands and a hosted adaptive loop are not offered by this connector.

Errors and recovery

Data and controls

Operator processes the account and workspace state, mission objective, run metadata, and artifacts needed for the requested work. Provider authorization is stored separately and encrypted at rest. Review the privacy policy for infrastructure providers, retention, and deletion requests. Remove provider access from your account and revoke the connector in your AI client when it is no longer needed.

For help, use Operator support or email info@blacklabelbots.com with your run ID and error code. Never include provider tokens or repository secrets.