open-browser-setup
v1.0.1
Published
Interactive installer for Open Browser — MCP server, CLI tool, skill, and Chrome extension setup
Maintainers
Readme
Open Browser Setup
Interactive installer for the Open Browser ecosystem. One command to set up everything you need to control your real Chrome browser with AI agents.
Quick Start
npx open-browser-setupThe installer walks you through:
- Package installation — MCP server, CLI tool, or both
- Skill installation — Claude Code
/open-browserskill for the CLI - MCP client configuration — auto-configures Claude Code, Cursor, Windsurf, Codex, OpenCode, or Pi
- Chrome extension — opens the Chrome Web Store for the Open Browser Bridge extension
What gets installed
MCP Server (open-browser-mcp)
58 browser automation tools exposed via the Model Context Protocol. Works with any MCP-compatible client (Claude Code, Cursor, Windsurf, etc.).
npm install -g open-browser-mcpCLI Tool (open-browser-cli)
Direct terminal commands for browser control. Token-efficient alternative to MCP — no tool registration overhead.
npm install -g open-browser-cliClaude Code Skill
The /open-browser skill loads on demand in Claude Code, giving the agent full browser control without consuming context window tokens for tool schemas.
Chrome Extension
The Open Browser Bridge Chrome extension connects the MCP server or CLI to your real browser via WebSocket + CDP.
Supported MCP Clients
| Client | Config File | Auto-configured |
|--------|-------------|:-:|
| Claude Code | ~/.claude/settings.json | Yes |
| Cursor | ~/.cursor/mcp.json | Yes |
| Windsurf | ~/.codeium/windsurf/mcp_config.json | Yes |
| Codex | ~/.codex/config.toml | Yes |
| OpenCode | ~/.config/opencode/opencode.json | Yes |
| Pi (omp) | ~/.omp/mcp.json | Yes |
Requirements
- Node.js >= 18
- Chrome (any recent version)
License
MIT
