How do I install Openchrome?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Openchrome need an API key?

No required environment variable is listed on this record.

What transport does Openchrome use?

Openchrome runs locally over stdio.

When was Openchrome last checked?

Last checked 2026-10-27. Open-source browser automation MCP server. Control your real Chrome from any AI agent.

Openchrome MCP サーバー

エージェントを強化

このサーバーを追加

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code PlugMCP で実行

キーとログ付きでコピーをホスト。

Local command

npx -y [email protected]

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add shaun0927-openchrome -- npx -y openchrome-mcp@1.15.0

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "shaun0927-openchrome": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

PlugMCP で実行

キーとログ付きでコピーをホスト。

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

起動

Server facts

Local

Transport: stdio
License: MIT
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

OpenChrome

OpenChrome is a browser automation MCP server for controlling a real Chrome browser from Claude Code, Codex CLI, OpenCode, or any MCP client.

It ships as a Node CLI plus MCP runtime. Desktop apps, browser extensions, native-host installers, deployment templates, and release artifact builders are outside this repository surface.

Install

Requires Node.js 20 or newer.

npm install -g openchrome-mcp
openchrome setup --client codex

For Claude Code:

openchrome setup --client claude

Restart the MCP host after setup so it reloads the generated configuration.

Run

openchrome serve --auto-launch --auto-elect --minimal

Manual Codex CLI configuration:

openchrome config --client codex

Add the printed [mcp_servers.openchrome] block to ~/.codex/config.toml.

CLI

OpenChrome can call its MCP tools directly from the shell:

oc run navigate --arg url=https://example.com
oc run read_page --arg mode=dom --json
oc navigate https://example.com
oc click ref_5

Playbooks run deterministic YAML scenarios:

oc playbook run scenario.yaml --vars url=https://iana.org --out report.md

HTTP Mode

Run a long-lived MCP HTTP daemon when multiple clients should share one managed Chrome owner:

openchrome serve --http 3100 --auth-token <token> --idle-timeout 30m
curl -s http://127.0.0.1:3100/health

Independent stdio clients should use separate --port and --user-data-dir profiles, or connect through broker mode with --auto-elect.

Both stdio and HTTP serve the stateless MCP 2026-07-28 revision alongside legacy initialize-based clients; see docs/mcp-2026-07-28.md.

Capabilities

Real Chrome control through CDP.
Navigation, clicks, typing, screenshots, DOM reads, accessibility reads, and natural-language element lookup.
Parallel tab/session workflows with broker-safe profile ownership.
Compact page serialization for lower-token agent loops.
Outcome contracts, evidence bundles, diffs, and diagnostics.
Optional pilot-tier recovery and skill runtime behind --pilot.

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

Documentation

Topic	Link
Architecture	`docs/architecture.md`
Getting started	`docs/getting-started.md`
CLI	`docs/cli.md`
Playbooks	`docs/cli/playbook.md`
MCP topologies	`docs/mcp/topologies.md`
MCP 2026-07-28 support	`docs/mcp-2026-07-28.md`
HTTP daemon	`docs/getting-started/http-daemon.md`
Security model	`SECURITY.md`
Repository structure	`docs/dev/project-structure.md`

Development

git clone https://github.com/shaun0927/openchrome.git
cd openchrome
npm install
npm run build
npm test

Useful checks:

npm run lint
npm run lint:repo-structure
npm run lint:tier
npm run docs:capability-map:check

License

MIT