# openchrome-mcp

> Open-source browser automation MCP server. Control your real Chrome from any AI agent.

- **URL**: https://www.freshcrate.ai/projects/openchrome-mcp
- **Author**: shaun0927
- **Category**: MCP Servers
- **Latest version**: `v1.12.7` (2026-06-04)
- **License**: MIT
- **Source**: https://github.com/shaun0927/openchrome
- **Homepage**: https://github.com/shaun0927/openchrome#readme
- **Language**: TypeScript
- **GitHub**: 183 stars, 29 forks
- **Registry**: npm (`openchrome-mcp`)
- **Tags**: `browser-automation`, `cdp`, `chrome`, `chrome-devtools-protocol`, `mcp`, `mcp-server`, `npm`, `openchrome`, `parallel-sessions`

## Description

Open-source browser automation MCP server. Control your real Chrome from any AI agent.

## Recent releases

| Version | Date | Urgency | Changes |
| --- | --- | --- | --- |
| `v1.12.7` | 2026-06-04 | High | Reliability hardening release on top of v1.12.6.  ## Fixes - **reliability:** the swallowed-error retry now actually fires, guarded by reconcile/timeout (L1, #1471). Closes the last open reliability retry-path defect.  ## Docs - **reliability:** reconciled the stale roadmap with shipped reality and recorded decisions D4/D5 (#1468). - **reliability:** corrected the E2E certification table — issues 13..18 implemented; 11/12/19/20/21 not yet (#1470, #1472).  Verified: `npm run build` (exit 0) + `te |
| `v1.12.6` | 2026-05-30 | High | ## OpenChrome MCP v1.12.6  A reliability- and multi-client–focused release. This cycle lands the **shared-profile broker** (multiple MCP clients safely driving one Chrome), a **central target-lease registry** that makes reconnect and concurrent control deterministic, a portable **outcome-contract** system with image QA and gate inspection, skill-memory **provenance + promotion**, and the **Online-Mind2Web / WebVoyager** live benchmark harness.  No breaking changes. Default tool surface remains * |
| `v1.12.5` | 2026-05-25 | High | # OpenChrome v1.12.5  Release date: 2026-05-25  ## Summary  v1.12.5 is the first release cut after the OpenChrome direction was clarified in SSOT issue #1359: **OpenChrome is a host-neutral MCP browser harness**. The release keeps the package focused on real Chrome control, deterministic MCP semantics, and portable evidence that can run under Codex, Claude Code, Hermes Agent, OpenClaw, and other MCP-capable hosts without assuming a specific agent runtime.  This patch integrates the full open PR |
| `v1.12.4` | 2026-05-17 | High | # OpenChrome v1.12.4  Release date: 2026-05-17  ## Summary  v1.12.4 is a benchmark release-safety patch. It does not claim that the competitive benchmark suite is ready to publish full live comparisons yet. Instead, it makes the remaining non-key blockers explicit and adds a fail-closed API-key-only readiness gate so maintainers cannot mistake available LLM/API credentials for complete benchmark readiness.  This release follows the v1.12.3 live benchmark execution-seam hardening work and adds th |
| `v1.11.0` | 2026-05-12 | High | # OpenChrome v1.11.0  Release date: 2026-05-12  ## Summary  v1.11.0 is the **portability-harness contract** release. It establishes a durable `core` / `pilot` tier split inside `openchrome-mcp`, ships a substantial batch of harness primitives in the core tier (no flag required), and stubs out the pilot tier behind a single `--pilot` opt-in flag. The release is backward-compatible: existing v1.10.x configurations keep working unchanged.  This release lands as a single cohesive publishable package |
| `v1.10.3` | 2026-05-05 | High | # OpenChrome v1.10.3  Release date: 2026-05-05  ## Summary  v1.10.3 is a publish-ready patch release that brings the validated `develop` line plus the `main` setup fixes into one release candidate.  The release focuses on making real-browser automation less fragile in the places where users were most likely to get stuck:  - Chrome now launches **headed by default** for `--auto-launch`, with explicit   headless opt-in for CI, Docker, and daemon-style environments. - Login and auth-redirect flows |
| `v1.10.2` | 2026-04-27 | High | # OpenChrome v1.10.2  Release date: 2026-04-23  ## Summary  v1.10.2 is a **patch release** focused on long-running process hygiene and steady-state resource usage.  This release pulls the validated `develop`-line runtime cleanup into the next publishable package and adds three follow-up resource fixes that were still open on the upstream tracker:  - stdio parent-death self-exit to prevent orphaned `openchrome-mcp` servers - bounded cookie caches to cap stale per-instance heap growth - health end |
| `v1.10.1` | 2026-04-23 | High | # OpenChrome v1.10.1  Release date: 2026-04-22  ## Summary  v1.10.1 is a **patch release** focused on stabilizing the v1.10.0 merge train, closing CI regressions, and shipping the merged reliability work in a cleaner, release-ready state.  This release consolidates the post-merge fixes around:  - tenant-aware HTTP session and metric propagation - explicit cookie-scan partial-result reporting - listener-failure cleanup and health visibility - aborted-call accounting for disconnected HTTP clients |
| `1.9.7` | 2026-04-21 | Low | Imported from npm (1.9.7) |
| `v1.9.7` | 2026-04-09 | Medium | ## v1.9.7 — Headless Cookie Persistence Fix  This release addresses a critical bug where headless mode failed to persist cookies and login state across restarts, causing repeated authentication prompts (e.g., Google login) that blocked automated workflows.  ### Bug Fixes  #### 🔐 Headless Cookie/Session Persistence ([#606](https://github.com/shaun0927/openchrome/issues/606))  **Root Cause A — Ephemeral temp profile for headless-shell** ([#609](https://github.com/shaun0927/openchrome/pull/609)) - |

## Citation

- HTML: https://www.freshcrate.ai/projects/openchrome-mcp
- Markdown: https://www.freshcrate.ai/projects/openchrome-mcp.md
- Dependencies JSON: https://www.freshcrate.ai/api/projects/openchrome-mcp/deps

_Generated by freshcrate.ai. Indexes npm releases for AI-agent ecosystem packages._