Browser MCP
An MCP server and Chrome extension that let the agent drive your already open browser with your logged-in sessions, all locally
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Controls your browser with active logged-in sessions
- Can act on external sites on your behalf
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/browser-mcpDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
This entry is high risk, so there is no one-click install. Review the code and add the config by hand.
Run in a terminal
claude mcp add --transport stdio browsermcp -- npx @browsermcp/mcp@latestOr add to the file .mcp.json, in the project
{
"mcpServers": {
"browsermcp": {
"command": "npx",
"args": [
"@browsermcp/mcp@latest"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"browsermcp": {
"command": "npx",
"args": [
"@browsermcp/mcp@latest"
]
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Run in a terminal
code --add-mcp '{"name":"browsermcp","type":"stdio","command":"npx","args":["@browsermcp/mcp@latest"]}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"browsermcp": {
"type": "stdio",
"command": "npx",
"args": [
"@browsermcp/mcp@latest"
]
}
}
}If the file already exists, add the server inside the servers key.
Run in a terminal
codex mcp add browsermcp -- npx @browsermcp/mcp@latestOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.browsermcp]
command = "npx"
args = ["@browsermcp/mcp@latest"]If the file already exists, append the block to the end.
Run in a terminal
gemini mcp add -s user browsermcp npx @browsermcp/mcp@latestOr add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"browsermcp": {
"command": "npx",
"args": [
"@browsermcp/mcp@latest"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"browsermcp": {
"command": "npx",
"args": [
"@browsermcp/mcp@latest"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"browsermcp": {
"command": "npx",
"args": [
"@browsermcp/mcp@latest"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"browsermcp": {
"command": "npx",
"args": [
"@browsermcp/mcp@latest"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"browsermcp": {
"type": "local",
"command": [
"npx",
"@browsermcp/mcp@latest"
]
}
}
}If the file already exists, add the server inside the mcp key.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"browsermcp": {
"command": "npx",
"args": [
"@browsermcp/mcp@latest"
]
}
}
}If the file already exists, add the server inside the context_servers key.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"browsermcp": {
"command": "npx",
"args": [
"@browsermcp/mcp@latest"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Install the Browser MCP Chrome extension, then add a browsermcp server to the MCP configuration using the npx command with the @browsermcp/mcp@latest argument.
Other ways from the author
{
"mcpServers": {
"browsermcp": {
"command": "npx",
"args": ["@browsermcp/mcp@latest"]
}
}
}Before the first run install the Browser MCP Chrome extension, otherwise the server has nothing to drive.
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 tabLimitations
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.
MCP
- Transport
- stdio
- Authentication
- not required
Security check
- Controls your browser with active logged-in sessions
- Can act on external sites on your behalf
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.
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.
Related
CLI, skill and Python library for browser control: the agent clicks, fills forms and reads pages over CDP
A skill that gathers the last 30 days of discussion on a topic from Reddit, X, YouTube, HN, Polymarket and GitHub into one brief
The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces
A fast Rust CLI for agent browser automation: accessibility snapshots with element refs, an MCP server and skills