Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Browser MCP Open my Gmail and read the latest email from my boss"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Browser MCP is an MCP server + Chrome extension that allows you to automate your browser using AI applications like VS Code, Claude, Cursor, and Windsurf.
Related MCP server: Browser MCP
⚡ Fast: Automation happens locally on your machine, resulting in better performance without network latency.
🔒 Private: Since automation happens locally, your browser activity stays on your device and isn't sent to remote servers.
👤 Logged In: Uses your existing browser profile, keeping you logged into all your services.
🥷🏼 Stealth: Avoids basic bot detection and CAPTCHAs by using your real browser fingerprint.
This repo builds and runs standalone. The internal monorepo packages the upstream
code depends on (@repo/* and @r2r/messaging) are reconstructed under
vendor/ and wired up through tsconfig.json path aliases, so no
private workspace packages are required.
npm install # installs deps and builds dist/ via the prepare hook
npm run build # (re)build dist/index.js
node dist/index.jsThe server communicates over stdio using the Model Context Protocol and opens a
WebSocket server on port 9009 that the Browser MCP Chrome extension connects
to. To use it with an MCP client, register the built binary — for example:
{
"mcpServers": {
"browsermcp": {
"command": "node",
"args": ["/absolute/path/to/dist/index.js"]
}
}
}After installing the Browser MCP Chrome extension, click its icon and press Connect on the tab you want to automate.
This repo contains all the core MCP code for Browser MCP. It was originally
developed inside a monorepo and depended on shared utils and types packages;
those have been vendored (see vendor/) so the project can be built
and run on its own.
Browser MCP was adapted from the Playwright MCP server in order to automate the user's browser rather than creating new browser instances. This allows using the user's existing browser profile to use logged-in sessions and avoid bot detection mechanisms that commonly block automated browser use.
Perform click on a web page
Inputs: ref (required), element (required).
Get the console logs from the browser
Inputs: no named parameters.
Go back to the previous page
Inputs: no named parameters.
Go forward to the next page
Inputs: no named parameters.
Hover over element on page
Inputs: ref (required), element (required).
Press a key on the keyboard
Inputs: key (required).
Take a screenshot of the current page
Inputs: no named parameters.
Select an option in a dropdown
Inputs: ref (required), values (required), element (required).
Capture accessibility snapshot of the current page. Use this for getting references to elements to interact with.
Inputs: no named parameters.
Type text into editable element
Inputs: ref (required), text (required), submit (required), element (required).
Wait for a specified time in seconds
Inputs: time (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 12 tools
Each tool targets a distinct browser action: navigation (navigate, go_back, go_forward), interaction (click, hover, type, select_option, press_key), state reading (snapshot, get_console_logs, screenshot), and waiting (wait). No two tools overlap in purpose, making selection unambiguous.
All tools follow a consistent verb_noun snake_case pattern with a uniform 'browser_' prefix. Verbs clearly describe actions (navigate, click, type, wait), making the naming predictable and easy to infer.
12 tools is a well-scoped set for a browser automation server. Each tool serves a distinct, essential function without unnecessary bloat or missing core capabilities, fitting the typical 3-15 range.
The tool set covers the full browser automation lifecycle: navigation, element interaction, state inspection, and output. Minor gaps exist such as no explicit 'get URL/title' or tab management, but the snapshot tool provides sufficient page state, so agents can work around these gaps.
AI-powered browser automation — navigate, click, fill forms, and extract data from any website.
Let your AI agent operate any website through a real, logged-in browser session.
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
Stealth web automation for AI agents. Login, signup, navigate, screenshot.
