Read workflow truth
Inspect runs, Workflow Cases, approvals, compare outputs, proof packs, and incident summaries without mutating anything.
Read-only MCP quickstart.
OpenVibeCoding is the command tower for AI engineering, and it already exposes a real Model Context Protocol (MCP) surface, but the public contract is intentionally read-only. This page exists so teams searching for MCP, Codex, Claude Code, or OpenClaw adoption paths can find the truthful protocol story quickly instead of guessing from source files.
Use this page when your first question is: “What can external tools safely inspect right now?” If your first question is instead about package imports, builder bootstrap, or repo-owned skills, this page should route you to the better next click.
What the current MCP surface is for
Return structured JSON
Expose a repo-owned protocol boundary that other tools and agents can consume safely instead of screen-scraping dashboard pages.
Stay below execution authority
Keep operator truth readable without inventing a second control plane, a hosted account layer, or write-capable MCP claims.
Fast adoption path
| My first question | Start here | Why |
|---|---|---|
| I need the shortest truthful protocol boundary | This page | Use MCP first when your team needs machine-readable inspection before packages or builder code. |
| I need the “which adoption ladder fits us?” answer | Compatibility matrix | Use it when the main question is whether you should start from MCP, skills, builders, or proof-first cases. |
| I also need HTTP, types, or a thin JS client | API and contract quickstart | Use the API page when you want the route/type/client edge in addition to the protocol story. |
| I need repo-owned builder packages | Builder quickstart | Use it when you are ready to import package-level helpers rather than only understand the protocol boundary. |
| I need coding-agent team guidance | Integration guide and skills quickstart | Use these when your real question is how a Codex / Claude Code / OpenClaw team should adopt the repo truthfully. |
Try the current server
The current server is a repo-owned stdio JSON-RPC node. Run it from the repo root when you want the shortest proof that the public MCP story is real:
Prerequisite: start from a bootstrapped OpenVibeCoding checkout. The wrapper expects the orchestrator Python dependencies to exist already, so run npm run bootstrap:host first when you are setting up a fresh clone.
bash /absolute/path/to/OpenVibeCoding/scripts/run_openvibecoding_readonly_mcp.sh
Current tool set:
list_runs,
get_run,
get_run_events,
get_run_reports,
list_workflows,
get_workflow,
list_queue,
get_pending_approvals,
get_diff_gate_state,
get_compare_summary,
get_proof_summary,
and get_incident_summary.
Want the client-specific config files after you prove the server is real? Open the agent starter kits for tracked Codex / Claude Code / OpenClaw setup snippets.
Need the machine-readable contract too? Open configs/mcp_public_manifest.json.
What to hand to any stdio-capable MCP client
If your client asks for a command, arguments, working directory, and environment instead of a hosted URL, use these repo-owned values directly.
| Field | Use this value | Why |
|---|---|---|
| Transport | stdio |
The shipped public MCP surface is a repo-owned stdio JSON-RPC server, not a hosted MCP account. |
| Working directory | the OpenVibeCoding repo root | The server reads repo-local runtime state, run bundles, and workflow truth. |
| Environment | wrapper-owned | The tracked wrapper exports PYTHONPATH=<repo-root>/apps/orchestrator/src so clients do not need to reconstruct the Python module path themselves. |
| Command | bash __OPENVIBECODING_REPO_ROOT__/scripts/run_openvibecoding_readonly_mcp.sh |
This is the shortest truthful startup command for stdio-capable clients today. |
| Auth boundary | repo-local read only | No hosted account, OAuth, or managed login layer exists in the current public contract. |
| Config template | examples/coding-agents/mcp/readonly.mcp.json.example |
This is the tracked shared config template used across the current Codex / Claude Code / OpenClaw starter surfaces. |
The wrapper keeps the public install story short, but the underlying runtime command stays
python3 -m openvibecoding_orch.cli mcp-readonly-server with
PYTHONPATH=<repo-root>/apps/orchestrator/src.
What it does not do yet
- no write-capable MCP mutations
- no hosted operator account or managed login layer
- no claim that MCP replaces the orchestration runtime itself
Why this matters for different audiences
Protocol-first inspection
Useful when a Codex-facing workflow needs one machine-readable place to inspect workflow truth before promoting package or skills adoption.
MCP-compatible workflow context
Useful when a Claude Code team wants the protocol layer to stay honest about what can be read today without implying write-enabled MCP.
Adjacent protocol layer
Useful as a read-oriented integration boundary around OpenClaw workflows, while plugin-ready wording stays separate from the current MCP story.
Where to read the current contract
- distribution status for release, package, and public-boundary truth
- AI + MCP + API surfaces for the broader product map
- compatibility matrix when your real question is which adoption ladder fits your stack
- agent starter kits when you need local config examples instead of architecture prose
- the public GitHub repo for source and release receipts, without treating internal markdown as the front door