openchrome

OpenChrome

OpenChrome is an MCP server that controls your real, already-logged-in Chrome through the CDP. It wraps the browser API with a hint engine, circuit breaker, auto-recovery runtime, and token-efficient page serialization.

What you can do

• Navigate — navigate url=<url> opens a URL in a managed tab.
• Read — read_page mode=dom returns a compact, ~5–15x token-cheaper serialization of the page. Use ref_N handles in follow-up actions.
• Interact — interact, fill_form, form_input, act for clicking, typing, and high-level actions.
• Screenshot — computer returns a screenshot of the current viewport.
• Parallel lanes — open multiple tabs with oc_lane_create; work them concurrently with the same Chrome session and existing cookies.
• Outcome contracts — oc_assert checks page state against a JSON contract (url equals, dom_count ≥ N, dom_text contains …) and returns pass / fail / inconclusive without guessing.
• Skills — oc_skill_record / oc_skill_recall store and replay procedural memory across sessions.
• Crawling — async crawl_start / crawl_status / crawl_cancel with cursor pagination.

Setup

npm install -g openchrome-mcp
openchrome setup               # Claude Code
openchrome setup --client codex   # Codex CLI

Restart your MCP client. Chrome auto-launches on the first tool call.

First tool by intent

Use this as the short routing card. The full catalogue remains in docs/agent/capability-map.md.

Default loop: navigate → read_page / oc_observe → interact → oc_assert → oc_evidence_bundle if the result is uncertain.

Use something else when:

• You need a deterministic browser script without an MCP host agent: use Playwright or Puppeteer.
• The user explicitly asks for a platform API or CLI: use that external tool.
• The next step is irreversible: get the host/user confirmation gate first.

Key tools

Full catalogue: docs/agent/capability-map.md.