Browser MCP
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
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
- Drives your browser with accounts already signed in
- Can act on external sites on your behalf
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/agent360dk-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 browser-mcp -- npx -y @agent360/browser-mcp@1.30.0Or add to the file .mcp.json, in the project
{
"mcpServers": {
"browser-mcp": {
"command": "npx",
"args": [
"-y",
"@agent360/browser-mcp@1.30.0"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"browser-mcp": {
"command": "npx",
"args": [
"-y",
"@agent360/browser-mcp@1.30.0"
]
}
}
}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":"browser-mcp","type":"stdio","command":"npx","args":["-y","@agent360/browser-mcp@1.30.0"]}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"browser-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@agent360/browser-mcp@1.30.0"
]
}
}
}If the file already exists, add the server inside the servers key.
Run in a terminal
codex mcp add browser-mcp -- npx -y @agent360/browser-mcp@1.30.0Or add to the file ~/.codex/config.toml, for all projects
[mcp_servers.browser-mcp]
command = "npx"
args = ["-y", "@agent360/browser-mcp@1.30.0"]If the file already exists, append the block to the end.
Add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"browser-mcp": {
"command": "npx",
"args": [
"-y",
"@agent360/browser-mcp@1.30.0"
]
}
}
}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": {
"browser-mcp": {
"command": "npx",
"args": [
"-y",
"@agent360/browser-mcp@1.30.0"
]
}
}
}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": {
"browser-mcp": {
"command": "npx",
"args": [
"-y",
"@agent360/browser-mcp@1.30.0"
]
}
}
}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": {
"browser-mcp": {
"command": "npx",
"args": [
"-y",
"@agent360/browser-mcp@1.30.0"
]
}
}
}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": {
"browser-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@agent360/browser-mcp@1.30.0"
]
}
}
}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": {
"browser-mcp": {
"command": "npx",
"args": [
"-y",
"@agent360/browser-mcp@1.30.0"
]
}
}
}If the file already exists, add the server inside the context_servers key.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"browser-mcp": {
"command": "npx",
"args": [
"-y",
"@agent360/browser-mcp@1.30.0"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Add the server: claude mcp add --scope user browser-mcp -- npx @agent360/browser-mcp@latest, then restart the client. Ask me to load the Chrome extension by hand, then verify the link with a screenshot of the current tab.
Other ways from the author
claude mcp add --scope user browser-mcp -- npx @agent360/browser-mcp@latestAfter the command, install the Chrome extension from the Chrome Web Store or load it unpacked, then restart the client.
This is third-party code. Review the repository files before installing.
What it does
Browser MCP is a Chrome extension paired with a local MCP server. The agent acts in the same browser where you are already signed in, so it works on sites with login walls, two-factor prompts and bot protection. When it needs a code from your inbox, a CAPTCHA, or consent for a sensitive step, it hands control back to you and waits. Several agents can run at once, each in its own tab group. Everything runs on your machine, with no account and nothing sent to the authors.
Who it is for. For developers and QA engineers who need to automate work in a real, already signed-in browser.
Good fit when
- You need to act on a site where you are already signed in, with no API to wire up
- You need to pass a login with an email code or CAPTCHA while keeping the sensitive steps yourself
- You need an end-to-end run through your own web app as a real user
Not a fit when
- A stable service API exists and is more reliable than browser automation
- You cannot give the agent access to a browser holding your live sessions
Example request
Open my dashboard tab, pull this month's numbers into a table, I will confirm the login code from my inbox myselfLimitations
You need both halves: the Chrome extension and the local server, and one without the other does nothing. Chrome will not install the extension by itself, so you load it once by hand or from the Chrome Web Store. The agent acts as you inside your sessions, so sensitive actions are worth confirming yourself.
How to disable. Remove the browser-mcp server from the agent's MCP config and disable or remove the extension in chrome://extensions.
MCP
- Transport
- stdio
- Authentication
- not required
Security check
- Drives your browser with accounts already signed in
- Can act on external sites on your behalf
README in short
The README describes a two-part tool: a Chrome extension and a local MCP server on npm. The core idea is that the agent works in your real, already signed-in browser, so it handles sites where ordinary automation gets blocked. It highlights the ability to stop and ask the human for a 2FA code or CAPTCHA. It supports concurrent sessions with color-coded tab groups and several built-in service integrations. Install is a claude mcp add command plus loading the extension by hand.
FAQ
How is this better than headless automation?
Actions run in your real Chrome with your sessions, so they pass where headless hits a login wall, CAPTCHA or bot protection.
Does data go to the authors?
No, the server runs locally, no account is needed, and the authors receive nothing.
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