Browser MCP
An MCP server and Chrome extension that let the agent drive your already open browser with your logged-in sessions, all locally
- 7,345 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Controls your browser with active logged-in sessions
- Can act on external sites on your behalf
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/browser-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Controls your browser with active logged-in sessions
- Can act on external sites on your behalf
This is third-party code. Review the repository files before installing.
What it does
Browser MCP is an MCP server plus a Chrome extension that lets the agent work inside your local browser instead of a separate headless instance. The server talks to the extension over a local websocket, so actions run on your machine and reuse your profile and existing logged-in tabs. The agent reads page structure through an accessibility-tree snapshot, navigates to URLs, clicks and types. It is adapted from Playwright MCP but aimed at the user's current browser. It connects to clients such as Claude, Cursor, VS Code and Windsurf.
Who it is for. For developers and testers who want the agent to act in their real browser with saved logins.
Good fit when
- You need to automate a site where you are already signed in, without logging in again
- You need to test a web flow in your own browser with a real profile
- You need the agent to read and parse an open page locally
Not a fit when
- You need an isolated headless browser for CI, where Playwright MCP fits better
- You cannot install the Chrome extension
Example request
Open the dashboard in my browser and collect the data from the table on the current tabMCP
- Transport
- stdio
- Authentication
- not required
Limitations
You need the Browser MCP Chrome extension and a running local browser. The repository itself notes it cannot be built standalone due to dependencies on a shared monorepo, so the published npm package is used. The agent works with your logged-in sessions, so scope its actions carefully. The last repository commit dates to April 2025, while the package remains in use.
How to disable. Remove the browsermcp entry from your client's MCP configuration and disable or remove the Browser MCP extension in the browser.
FAQ
Does data go to a server?
No, automation runs locally between the server and the extension, and browser activity stays on your device.
Do I need a separate browser?
No, the server works with your normal browser and current profile, so existing logins are available.
Discussion
No questions or reviews yet.
Related
MCP serversA Chrome extension with an MCP server: the agent drives your everyday browser with its sessions, tabs, bookmarks and history
An MCP server that drives your already open Chrome and stops to ask you about a 2FA code, a CAPTCHA, or a choice only you can make
An MCP server that lets an agent drive a real browser: open pages, click and fill forms through Playwright
A local browser automation platform: MCP server, CLI and skills so an agent can drive Chrome, fill forms and pull data from pages
Microsoft's official MCP server for driving a browser with Playwright through the accessibility tree, no screenshots needed
An MCP wrapper over the browser-use engine: a single tool drives a browser from a natural-language task.
README in short
The README describes Browser MCP as an MCP server together with a Chrome extension for browser automation from AI clients, among them VS Code, Claude, Cursor and Windsurf. It stresses local operation without network latency, privacy, using the current profile with active sessions, and getting past basic bot detection thanks to a real browser fingerprint. The project is adapted from Playwright MCP to drive the user's browser rather than spawn a new instance. The repository holds the core server code but cannot be built standalone due to shared monorepo dependencies. Apache 2.0 license.