This page exists for the moment after a team says: “We understand the boundary. Now give us the exact starter files.” The kits below keep OpenVibeCoding truthful: read-only MCP, repo-owned skills/bootstrap files, and builder-safe entrypoints for Codex, Claude Code, and OpenClaw.
These are starter kits, not official plugin/store packages. They are the narrowest repo-owned way to make adoption easy without inventing a hosted product, a marketplace listing, or public write-capable MCP.
The fastest truthful setup is still a real OpenVibeCoding clone. OpenVibeCoding is the command tower for AI engineering, but these kits still assume you are wiring the client from the repo root or from a vendored workspace copy.
The shipped public MCP server is still read-only. Queue preview/cancel and the queue-only pilot server remain guarded repo-operator groundwork, not the public promise.
Codex and Claude Code use real MCP configuration paths, and OpenClaw exposes a real MCP registry path, but none of that turns OpenVibeCoding into an official marketplace item today.
The truthful short path is still: prove the repo-local path first, then paste one host-tool starter, then verify the proof loop again. That keeps adoption honest and stops one copied config file from pretending it already proved a real integration.
npm run bootstrap:host
OPENVIBECODING_HOST_COMPAT=1 bash scripts/test_quick.sh --no-related
npm run devThis repo-local full-stack path starts the orchestrator API and the dashboard together on localhost, so the browser can use the operator loop without exposing a bearer token on the client.
Expected success today:
the quick path finishes cleanly, the orchestrator API plus dashboard start together, and the
proof-first use-case loop still routes you
to Workflow Cases, Proof & Replay, and the tracked
news_digest proof assets.
If you are iterating on the dashboard shell only, keep npm run dashboard:dev
for the frontend after the API is already running in another terminal.
| Client | Official host surface | Current OpenVibeCoding status | Safest wording today |
|---|---|---|---|
| Codex | Official plugins surface exists. See OpenAI Codex plugins. | Public starter docs, one local marketplace example, and one portable local bundle exist. No official listing or submission receipt is tracked here today. | Codex-compatible starter / manual-marketplace-compatible / not officially listed |
| Claude Code | Official marketplace, submit, and review flow exist. See plugins and discover plugins. |
Public starter docs and a local --plugin-dir
bundle seed exist. No official marketplace submission receipt
is tracked here today.
|
Claude Code-compatible starter / not listed |
| OpenClaw | Official ClawHub public registry exists. See ClawHub. | Public starter docs plus a compatible local bundle path exist. The matching adoption-router skill is already live on ClawHub, and the official model remains publish-first rather than review-queue-first. | OpenClaw-compatible starter / ClawHub skill live |
| Client | Fastest setup | Tracked starter file | Official config reference |
|---|---|---|---|
| Codex | Use codex mcp add for a repo-root stdio server or drop the TOML snippet into ~/.codex/config.toml / .codex/config.toml. |
codex/openvibecoding.config.toml | OpenAI Codex MCP docs |
| Claude Code | Use claude mcp add --transport stdio --scope project for the fastest team-safe setup, or check in a project .mcp.json. |
claude/project.mcp.json | Claude Code MCP docs |
| OpenClaw | Use openclaw mcp set with one JSON object when you want OpenClaw-managed outbound MCP server definitions. |
openclaw/openvibecoding-server.json | OpenClaw MCP docs |
Fastest raw direct CLI wiring if you are not copying the tracked config file yet:
codex mcp add openvibecoding-readonly \
-- bash /absolute/path/to/OpenVibeCoding/scripts/run_openvibecoding_readonly_mcp.shNeed a durable config file instead of a one-line add command? Start from the tracked Codex example. That tracked file is the canonical wrapper-based template.
Fastest raw direct CLI wiring if you are not copying the tracked project file yet:
claude mcp add --transport stdio --scope project \
openvibecoding-readonly \
-- bash /absolute/path/to/OpenVibeCoding/scripts/run_openvibecoding_readonly_mcp.sh
If you want the team-visible file checked into the repo root, start from
the tracked project .mcp.json example.
That tracked file is the canonical wrapper-based template.
Fastest OpenClaw-managed saved definition:
openclaw mcp set openvibecoding \
'{"command":"bash","args":["/absolute/path/to/OpenVibeCoding/scripts/run_openvibecoding_readonly_mcp.sh"],"cwd":"/absolute/path/to/OpenVibeCoding"}'Need the JSON object as a tracked file first? Start from the tracked OpenClaw example.
| Client | Install step you just finished | Next proof check | Success signal today |
|---|---|---|---|
| Codex | Added the repo-root read-only MCP server or copied the local marketplace seed. | Route back through the public use-case guide and confirm the same proof-first loop still makes sense for your repo clone. | The repo-local quick path is still healthy, the starter points at the same repo root, and you are not relabeling a local bundle as an official listing. |
| Claude Code | Added the project .mcp.json or copied the local --plugin-dir seed. |
Copy the tracked openvibecoding-proof command from the Claude example, then use it to route back to Workflow Cases, Proof & Replay, and the tracked news_digest assets. |
You can keep the repo-local proof-first loop, the project config stays read-only, and the Claude starter is still described as local/project adoption rather than a marketplace listing. |
| OpenClaw | Saved the JSON server object or merged the tracked TOML bundle path into your OpenClaw config. | Use the same public use-case guide as the proof target and keep the OpenClaw story on the read-only proof/replay side. | The bundle path resolves to your local clone, the MCP server stays read-only, and you still describe the result as bundle-compatible rather than live on ClawHub. |
MCP config is the narrowest setup, but the repo also ships one compatible local bundle for teams that want the same starter pack to stay portable across Codex, Claude Code plugin-dir development, and OpenClaw bundle loads.
| Client | Tracked path | How to use it truthfully |
|---|---|---|
| Codex |
codex/marketplace.example.json
+ examples/coding-agents/plugin-bundles/openvibecoding-coding-agent-bundle/
|
Copy the tracked local marketplace seed, replace its __OPENVIBECODING_REPO_ROOT__ placeholder with the absolute path to your repo checkout, then keep the same read-only MCP server definition beside it. |
| Claude Code | examples/coding-agents/plugin-bundles/openvibecoding-coding-agent-bundle/ |
Use the same bundle for local --plugin-dir development, or keep the lighter project-local .claude + .mcp.json path when plugin packaging is unnecessary. |
| OpenClaw |
openclaw/config.openclaw.example.toml
+ examples/coding-agents/plugin-bundles/openvibecoding-coding-agent-bundle/
|
Load the same compatible bundle through plugins.load.paths and keep OpenVibeCoding positioned as the proof / replay / read-only layer rather than a published registry item. |
Start from AGENTS.md when you want the repo's real safety rails, docs-first order, and finish-the-job contract.
Use the root README.md plus the public route pages to stay on the truthful public surface without pulling in maintainer-only material.
Use policies/agents/codex/AGENTS.openvibecoding.md when you want a narrower Codex-governed seed file beside the repo-wide contract.
Need the broader explanation first? Route back through the integration guide, skills quickstart, read-only MCP quickstart, and builder quickstart.
Need more than a single MCP config snippet? The repo now also keeps
a tracked examples/coding-agents/ tree for local bundle
and project-level starter material.
Use the tracked local bundle example when you want a repo-owned Codex-compatible bundle without claiming a published directory listing.
Use the tracked slash-command, reviewer, project .mcp.json, and shared bundle examples when you want a truthful Claude Code starter without claiming a published marketplace item.
Use the tracked OpenClaw README plus the same compatible local bundle when you want a truthful OpenClaw-side adoption story that stays below published registry claims.