About AutoBrowser MCP
AutoBrowser MCP is an MCP server and Chrome extension for AI applications that need to control a user's existing browser session. It runs locally and gates access through explicit pairing and extension-enforced restrictions.
Key features
- 01Control Chrome tabs with Playwright
- 02Use signed-in sites and profiles
- 03Pair through a six-digit code
- 04Block restricted pages and stopped sessions
Use cases
- 01Automate tasks in signed-in websites
- 02Let an AI app operate separate browser tabs
MCP support
The MCP server forwards an AI application's browser tool calls to a local daemon, which controls tabs through the extension.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEBrowser MCP
Browser MCP lets AI apps (Claude Code, Cursor, VS Code, Codex, Claude Desktop…) use your own Chrome: your signed-in sites, your profile, in tabs of their own. Everything runs on your computer.
- Website and docs: browsermcp.io, docs
- Extension: Chrome Web Store, or build it yourself
- MCP server:
@browsermcp/mcpon npm
How it works
Each AI app runs the MCP server (npx @browsermcp/mcp@latest), a small process that starts one daemon per user and forwards the app's browser tool calls to it. The daemon drives the browser's tabs with Playwright, through the extension: a thin chrome.debugger relay that only talks to the daemon on 127.0.0.1, and only after you click Allow in its popup once per computer, having checked that its six-digit code matches the one your AI app shows. The extension enforces its own rules whatever the daemon asks: no incognito, browser or extension pages, and nothing while you've pressed Stop.
| Folder | Package | |
|---|---|---|
packages/mcp | @browsermcp/mcp | The MCP server and the daemon (README) |
packages/protocol | @browsermcp/protocol | The protocol between the extension and the daemon, including pairing |
packages/extension-core | @browsermcp/extension-core | The extension's browser control: the connection, pairing, the debugger relay, the rules about tabs, tab groups, the badge |
apps/extension | @browsermcp/extension | The extension built from this repo: browser control and its popup |
Build it yourself
You need Node.js 24 or later, pnpm (corepack enable) and Chrome or another Chromium browser (Edge, Brave, Arc…). Firefox has no debugger API, so Browser MCP doesn't work there.
-
Build the extension and the server:
git clone https://github.com/BrowserMCP/mcp.git browsermcp cd browsermcp pnpm install pnpm build -
Open
chrome://extensions, turn on Developer mode, click Load unpacked and pickapps/extension/.output/chrome-mv3. It's called "Browser MCP (self-built)". If the Chrome Web Store's Browser MCP is installed in the same profile, turn it off, since only one of them can use the server at a time. -
In your AI app's MCP config, run the server you built instead of the one on npm:
{ "mcpServers": { "browsermcp": { "command": "node", "args": ["/path/to/browsermcp/packages/mcp/dist/index.js"] } } }npx @browsermcp/mcp@latest(the docs' setup) works with this extension too: it's the same server, published from this repo. -
Restart the AI app and ask it to do something in the browser. The first time, the extension's popup asks you to Allow the server on this computer: check that its code matches the one the AI app shows.
Every build of this extension has the same ID (imlplcjlhgpajopdbpbngiadkcmdbgob, from the key in apps/extension/extension-key.ts), which the server accepts besides the Chrome Web Store's. A build with another key needs its ID in BROWSER_MCP_EXTENSION_IDS (comma-separated) in the server's environment, or on a line of ~/.browsermcp/dev-extension-ids.
Updating
git pull
pnpm install
pnpm build
Then click the reload button on "Browser MCP (self-built)" in chrome://extensions, and restart your AI apps if they run the server from this folder. The extension and the server tell you when the other side is too old for them.
Development
pnpm lint,pnpm format(pnpm format:fixfixes it): Oxlint and Oxfmt.pnpm typecheck,pnpm test: TypeScript and the unit tests (Vitest) of every package. The server's tests run Playwright's Chromium: install it once withpnpm --filter @browsermcp/mcp exec playwright-core install chromium.pnpm smoke: builds the extension in development mode and the server, loads the extension in headless Chromium and drives it through the server as an AI app would, on random ports and a temporaryBROWSER_MCP_HOME, so it never touches your own Browser MCP. Screenshots go toapps/extension/.output/smoke/.pnpm --filter @browsermcp/extension build:dev: a development build (apps/extension/.output/chrome-mv3-dev).
Contributing and security
See CONTRIBUTING.md for how to report bugs and send changes, and SECURITY.md to report a vulnerability privately.
License
Apache-2.0. "Browser MCP" and its logo are the project's trademarks: if you publish a modified extension or server, give it another name and icon (TRADEMARKS.md).
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.