# claw-orchestrator [Health: Active]

**Category:** 🤖 Coding Agents  
**Repository:** https://github.com/Enderfga/claw-orchestrator  
**GitHub Stars:** 596  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/claw-orchestrator

## Description
Run Claude Code, Codex, Antigravity, Grok Build and OpenCode behind one runtime, and a run only counts as done when checks it didn't write pass. Cross-engine fan-out, councils, session handoff, spend caps, MCP server, ACP agent.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "claw-orchestrator": {
    "command": "npx",
    "args": ["-y","-p","@enderfga/claw-orchestrator","clawo-mcp"]
  }
}
```

## Documentation

## What claw-orchestrator does

The claw-orchestrator MCP server exposes a headless runtime for coding agents through MCP, alongside a CLI, an OpenAI-compatible endpoint, a TypeScript SDK, and an ACP agent. It can place Claude Code, Codex, Antigravity, Grok Build, OpenCode, and custom command-line agents behind one interface. The project fits the Coding Agents category because its primary job is coordinating agents that modify and test software.

Persistent sessions retain conversation context, tools, models, and worktree settings across requests. A fan-out operation sends a task to several engines, while session handoff moves an active conversation to another engine or model in the same workspace. Durable workflows checkpoint state so they can be resumed, retried, timed out, cancelled, or steered after interruptions.

Verification is based on an acceptance contract rather than the agent's report. Contracts can include commands, HTTP probes, screenshots, diff rules, and file assertions. The runtime executes the declared checks, reads their results, and stores evidence on disk. A run with a contract is classified as `verified`, `refuted`, or `unverified`; changing the tests used by a contract refutes the run.

## How it works

The runtime is started locally with `clawo serve` and provides a dashboard on `127.0.0.1:18796`. The CLI can start a solve workflow, select an engine, attach one or more checks, wait for completion, inspect a run, and list recent activity. The MCP path uses `clawo-mcp`; an MCP host can request `workflow_start` with the `solve` template, a task, and a contract containing check definitions.

Each engine must be installed and authenticated separately. The supported built-in engine names shown in the setup instructions are `claude`, `codex`, `agy`, `grok`, and `opencode`. The runtime records every engine turn, including model, token, cost, and verdict information. A `maxBudgetUsd` limit can be enforced across engines.

## Setup and configuration

Install the package globally with npm, then run the local service:

```bash
npm install -g @enderfga/claw-orchestrator
clawo serve
```

Node 22 or newer is required, along with at least one supported engine CLI installed and logged in. The server writes an access token to `~/.openclaw/server-token`, which the CLI reads. To connect an MCP host such as Claude Code, register the stdio server with:

```bash
claude mcp add clawo -- clawo-mcp
```

The TypeScript SDK can also create a `SessionManager`, start a session with an engine and working directory, and send messages to that session. Browser access uses the local dashboard login URL with the generated token.

## Tools and capabilities

The claw-orchestrator MCP server supports these documented areas:

- Start solve workflows with tasks and acceptance contracts.
- Maintain long-lived coding-agent sessions.
- Fan out a request to multiple engines and optionally synthesize results.
- Transfer a live session to another engine or model.
- Resume, retry, cancel, steer, and time out checkpointed workflows.
- Run checks independently and inspect changed files and failure reasons.
- Apply per-run or cross-engine spend limits and view the turn ledger.

## Limitations and notes

The runtime does not replace the underlying engine CLIs: at least one must be installed and logged in before use. Its verification result depends on the checks declared in the acceptance contract and the runtime's ability to execute them. The README describes local operation, with the dashboard bound to `127.0.0.1:18796`; it does not document hosted deployment or additional authentication providers.

The claw-orchestrator MCP server is one access path among several. ACP support is intended for Zed, JetBrains, and other ACP editors, while MCP support depends on the host's MCP connection features. The README does not establish that every listed engine supports every workflow or contract type.

_Full upstream README: https://allmcps.com/mcp/claw-orchestrator/readme_