0xdead4f/openbrowser-mcp

A browser-automation MCP server for coding agents. Any Chromium browser, every profile at once, no domain blocklist.

About openbrowser-mcp

A zero depedencies Claude in Chrome clone that attaches to your real browser profile. Any Chromium browser, every profile at once, no domain blocklist.

Explanation · Installation · Tools · License

An MCP server that drives real Chromium browsers over the Chrome DevTools Protocol, so a coding agent can open a page, click through it, fill forms, read the console and network log, and pull back whatever the page loaded.

It attaches to your existing profile rather than launching a clean automation profile. Whatever you are already logged into, the agent can use — no separate login flow, no cookie export. There is no domain blocklist.

- Many profiles at once. A detached broker process lets several agent sessions share one browser, and serves Chrome Default + Chrome work + Brave simultaneously. Each profile gets a stable id; browserselect pins one per agent session. - Refs, not screenshots. pageoutline or readpage hand back element refs like e214 that you pass straight to computer({action:"leftclick", ref:"e214"}). A screenshot costs ~1,296 tokens; a readpage is roughly 15× cheaper. Take a screenshot when you need to see something, not to locate it. - Big things go to disk. sourcesdownload writes files to a tree and returns only counts and a manifest path, so a 100 MB download never becomes a 100 MB string in context. - Incognito windows are supported, but all of them share one session: separate windows give you separate tab groups, not separate logins. Use separate profiles for isolated cookie jars.

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/0xdead4f--openbrowser-mcp.html)

Related MCP servers