Power your agent
पब्लिशर की अपनी कमांड। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
npx -y @agent360/[email protected]Claude Code में लोकल कमांड के लिए इंस्टॉल लिंक नहीं है। नीचे दी गई कमांड कॉपी करें और टर्मिनल में चलाएँ।
claude mcp add agent360dk-browser-mcp -- npx -y @agent360/browser-mcp@1.31.0टर्मिनल में चलाएँ।
{ "mcpServers": { "agent360dk-browser-mcp": { "command": "npx", "args": [ "-y", "@agent360/[email protected]" ] } }}claude_desktop_config.json
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चपब्लिशर से
The browser tool that can stop and ask you. A 2FA code, a CAPTCHA, a choice only you can make: it asks on your own screen, then carries on in the same signed-in Chrome.
It drives the Chrome you are already signed into: no login step to fail, no API key to wire up, no fresh profile that is a stranger to every account you have. Up to 20 agents at once, each in its own colour-coded tab group. 40 tools, MIT, runs on your machine.
The browser tool that can stop and ask you. A 2FA code, a CAPTCHA, a choice only you can make: it asks on your screen, then carries on in the same signed-in Chrome. 40 tools, MCP clients that run local servers, MIT.
→ What it can and cannot get past - every wall, marked measured, by design, not yet, or won't. Including the ones we have not fixed.
Browser MCP gives Claude Code (and MCP clients that run local servers, such as Cursor and VS Code agent mode) control of your actual Chrome: your cookies, your sessions, your 2FA. So it works on CAPTCHA, 2FA and anti-bot sites where Playwright and Puppeteer get blocked - because it's you browsing.
The killer move: it hits a login wall, opens your Gmail, reads the verification code, and continues the sign-in. There is no email API to set up. Operate platforms with no API, QA your own web app end-to-end, or work dashboards, LinkedIn and Reddit at human pace - with you approving the sensitive steps.
40 tools. Auto-clicks the reCAPTCHA v2 checkbox, with a human fallback for the rest. Multi-session color-coded tab groups. MIT, free, and it runs on your machine - no account, no telemetry, nothing sent to us.
Rather not do it by hand? Paste this to your AI assistant - Claude Code, Cursor, Codex, VS Code, Windsurf, Cline - and it sets itself up:
Set up Browser MCP for me. Read https://browsermcp.dev/llms-install.md and follow it for whichever AI client you are running in. One step only I can do - tell me which one, and wait for me. When I confirm, call
browser_list_tabsto prove both halves are talking.If you cannot open URLs:
npx @agent360/browser-mcp install
It reads the same guide the four steps below spell out by hand. One step stays yours either way: Chrome will not let an extension install itself, so you load it once.
1 - Install the Chrome extension. One click from the Chrome Web Store; Chrome keeps it updated. No store? See the unpacked install below.
2 - Add the MCP server. Paste this in a terminal. Required - the extension does nothing on its own:
claude mcp add --scope user browser-mcp -- npx @agent360/browser-mcp@latest
3 - Restart Claude Code. That is what starts the server. The extension shows no badge until step 4 - the server only takes a port the first time your agent actually uses the browser. A green badge with the number of connected agents appears then; nothing on the icon before that is normal. (The icon itself never changes colour - it is the badge that turns green.)
4 - Say this, to check it worked. Paste it to Claude Code:
Open example.com and take a screenshot.
You get an image back instead of "I don't have browser access". That's it - you're running. → What else to say
Using Cursor, VS Code, Codex or Windsurf? Same server, that client's own config - the prompt at the top handles it, or see browsermcp.dev/docs. Everything below is the long version.
Browser MCP is two halves and you need both: a Chrome extension (drives the browser) and a local MCP server (what your agent actually talks to). Installing only the extension - e.g. straight from the Chrome Web Store - leaves it stuck on "Not connected", because there is no server for it to reach. Chrome cannot install the server, and npm cannot install the extension. Hence two steps.
claude mcp add --scope user browser-mcp -- npx @agent360/browser-mcp@latest
That is Claude Code's own MCP command, so the entry lands in the config Claude Code actually reads. --scope user makes it available in every project.
Want the extension files on disk for the unpacked install in Step 2? Also run:
npx @agent360/browser-mcp install
It copies the extension to ~/.browser-mcp/extension/ and prints that path in the terminal - copy it. (It also registers the server with Claude Code, Codex, VS Code and Cursor if it finds them.)
Chrome won't let extensions install themselves from npm - you load it manually one time. To update later, re-run the install command and reload it (see Keeping it updated). Prefer the Chrome Web Store install if you'd rather have the extension auto-update.
chrome://extensions in the address bar~/.browser-mcp/extension/ and click "Select"
Cmd+Shift+G in the file picker, paste ~/.browser-mcp/extension/, press Enter%USERPROFILE%\.browser-mcp\extension\ in the address bar (Windows is not yet verified: our automated tests do not pass there)~/.browser-mcp/extension/ in the path fieldThat's it. The Browser MCP icon will appear in your toolbar, and 40 browser tools are now available in Claude Code.
If you don't want to use npm, download the extension directly:
agent360-browser-mcp-<version>.zip) from the latest GitHub release~/Downloads/browser-mcp-extension/)~/.browser-mcp/extension/claude mcp add --scope user browser-mcp -- npx @agent360/browser-mcp@latest, or add this to ~/.claude.json by hand:
{
"mcpServers": {
"browser-mcp": {
"command": "npx",
"args": ["@agent360/browser-mcp@latest"]
}
}
}
This replaces Step 2 only - you still need Step 1.
claude mcp add --scope user browser-mcp -- npx @agent360/browser-mcp@latest
Skip step 2 and the extension icon will sit on "Not connected" forever - that is the symptom of a missing MCP server, not a broken extension.
Nothing happens until you ask, and the hardest part of a new tool is knowing what to ask for. Paste one of these to your agent (where it says example.com, put your own site):
The pattern: many of the browser tasks you would do yourself, on sites you are already signed into. It is strongest where there is no API - internal dashboards, admin panels, portals, LinkedIn. Built something good? Add it to the gallery.
The reason this works where headless dies is not that it slips past anything. It is that there is nothing to slip past: it is your Chrome, your session, your consent. What is left is the hard part - pages that fight any automation because of how they are built.
Every release is gated on a flow test against a real Chrome that has to survive exactly those: all 40 tools are exercised, and the gate also checks that the extension Chrome is running is the one being released - not another copy with the same version number. The failures that do show up are honest ones: mouse events are not delivered to a tab that is not in front, and the tools say so instead of reporting success. What the test covers
fill sticks in a React-style controlled fieldclick refuses a 0×0 element instead of hitting (0,0), and says so
when the page never took the eventIn a tab you are not looking at, the agent can navigate, read, screenshot, run scripts, click,
and fill a field it finds by CSS selector. Chrome does not deliver mouse and keyboard events to a
tab that is not the visible one in its window, so key presses, hover, double-click, right-click,
coordinate clicks, combobox typing, and filling a field found by its text all fail with an error
that says so. The agent can then call browser_switch_tab, which makes that tab the active one in
its window, but since 1.30.2 it does not bring Chrome in front of you. Input that needs Chrome in
front can then still fail, and the
agent asks you first: only with bring_to_front: true does Chrome come forward. A screenshot of a
window covered by other windows likewise answers window-covered instead of raising Chrome.
Those tools measure whether the page actually received the event rather than trusting Chrome's acknowledgement, so a background tab produces an honest failure instead of a silent one. (Introduced in 1.29.2 - see CHANGELOG.md for which release you are on.)
Fully hands-off background input is not part of 1.30, and it is not something we can fix: Chrome
delivers no mouse or keyboard input to a tab that is not the visible one in its window (measured).
Whether it does to the active tab of a window without the operating system's focus is unmeasured in
desktop Chrome, so the tools' landed answer decides. Some of it cannot be solved at all: CSS
:hover is a state the renderer owns and no script can fake it, a script-dispatched event is
never isTrusted, elementFromPoint stops at a cross-origin iframe, and the text selection a
real double-click makes is browser behaviour rather than an event.
That last group matters most. A tool that quietly reports success is worse than one that fails, because you build on the answer. Where we still fall short of it, it is written down: see #19.
Corrected 2026-09-07, and again 2026-09-19. This table used to say Playwright MCP was headless and made you log in every time. That was wrong. The row we then called "the one that survives" - concurrent clients conflicting on one profile - was wrong too: that limitation belongs to their persistent-profile mode, and their Chrome extension explicitly gives each connected client its own coloured tab group, which is the same mechanism we describe on our own row. We had corrected one page and not the pattern. The row that actually survives is human-in-the-loop, and it is the one we measured: the Playwright MCP README lists 72 documented tools (counted 2026-09-19) and none of them can stop and ask the person for a code.
On the name: the similarly-named
browsermcp.io(@browsermcp/mcp) is a different, unaffiliated project with no commits since April 2025. This is Browser MCP by Agent360 (@agent360/browser-mcp) - actively maintained. Full side-by-side →
All three are optional. None is needed for normal use.
Each Claude Code conversation gets its own MCP server on a unique port (9876-9895). The Chrome extension connects to all active servers simultaneously.
Need more than 20 at once? The range is a setting, not a hard limit, but both halves have to agree.
Set BROWSER_MCP_MAX_PORT in every chat's MCP config, set bmcpPorte to the same range in the
extension's storage, then reload the extension: it reads the range only when it starts. Change only the
server side and chat 21 binds a port the extension never looks at, so the browser goes quiet in that chat
with nothing to explain it. 100 is plenty; the hard cap is 200. Every extra port costs your browser one
refused connection every two seconds, whether you use it or not, so do not widen it for fun.
Claude Session 1 ←(stdio)→ MCP :9876 ←(WS)→
Claude Session 2 ←(stdio)→ MCP :9877 ←(WS)→ Chrome Extension → Browser
Claude Session 3 ←(stdio)→ MCP :9878 ←(WS)→
The extension only connects to 127.0.0.1, deliberately - it will not talk to a remote
WebSocket. If your MCP gateway runs on a different box than your browser, forward the port
range over SSH.
Recipe below contributed by @bkuri,
who ran into exactly this and solved it. Linux + systemd; needs autossh locally and your
public key already on the server:
# ~/.config/systemd/user/browser-mcp-tunnel.service
[Unit]
Description=SSH tunnel for browser-mcp WebSocket (ports 9876-9895)
After=network-online.target
Wants=network-online.target
[Service]
Type=simple
ExecStart=/bin/sh -c '/usr/bin/autossh -M 0 -N \
-o ServerAliveInterval=30 -o ServerAliveCountMax=3 \
-o ExitOnForwardFailure=yes -o LogLevel=ERROR \
$(for p in $(seq 9876 9895); do printf " -L %s:127.0.0.1:%s" "$p" "$p"; done) \
server-name'
Restart=on-failure
RestartSec=5
Environment="AUTOSSH_GATETIME=0"
[Install]
WantedBy=default.target
Replace server-name, then systemctl --user enable --now browser-mcp-tunnel.service.
The original recipe listed ports 9876-9885 by hand - the range was ten back then. It is twenty now, so the loop above generates them instead of hard-coding a list that goes stale the next time the range changes.
browser_extract_token opens the provider's API page and returns instructions for finding or creating the credentials. It reads nothing itself, and for HubSpot, Slack, Shopify and LinkedIn the page is a settings or app list on the way to the token, not the token page itself. Any other provider answers Unknown provider.
extension/
manifest.json # Manifest V3
background.js # Service worker - Chrome API dispatcher, session tab groups
offscreen.js # Persistent WebSocket bridge (multi-port scanning)
popup.html/js # Status UI - sessions, tabs, action log
mcp-server/
index.js # MCP server (stdio) + WebSocket client
tools.js # 40 tool definitions
bin/cli.js # Install CLI
Browser MCP has two parts, and they update independently - how the extension updates depends on how you installed it:
Not sure which you have? Open chrome://extensions and find Browser MCP. If it shows a "Loaded from /path/…" line, it's unpacked (manual updates). If there's no such line, it came from the Chrome Web Store (auto-updates).
Want zero-maintenance updates? Install the extension from the Chrome Web Store, then run claude mcp add --scope user browser-mcp -- npx @agent360/browser-mcp@latest to register the server. After that, both parts stay current on their own - as long as your config uses @agent360/browser-mcp@latest.
"Chrome extension not connected"
chrome://extensionsScreenshot fails
browser_reattach_debugger and try againClick doesn't work on SPA
browser_click("text=Submit")Upload fails with "Not allowed"
file-access-off unless Chrome confirms that file access is onStale processes
lsof -i :9876-9895 | grep LISTENBrowser MCP is built in the open and shaped by the people using it.
Or just ask Claude - it knows about the browser_about tool and will draft the report and hand you a link to review and submit when you say things like "I wish browser-mcp could …" or "share my browser-mcp use-case".
The Chrome Web Store ranks on ratings, and we have none - so a sentence from you moves this further than anything we can write. Leave a review if it earned one, and say so honestly if it did not. No signup, no reward, nothing gated behind it - we just have no signal at all right now.
This drives your browser. Computer MCP drives everything else on macOS - menus, windows, the Dock, any app's accessibility tree - with the same stance: password fields are blacked out in memory before a screenshot is written, writes go through a consent gate, and every action lands in an append-only log. It runs in the background by default: the tools that could take over your screen are not offered unless you ask for them.
npx @agent360/computer-mcp · MIT · macOS.
The point of this tool is that your browsing stays in your browser. There is no account and no server of ours between you and the page.
browser_get_cookies, browser_get_local_storage,
browser_extract_token), two more write them (browser_set_cookies,
browser_set_local_storage), and three more can get
to the same data another way: browser_execute_script runs in the page and
can read document.cookie, and browser_get_page_content and
browser_extract_list will carry a token that the page itself puts in the
DOM. When any of them runs, that value goes to your MCP client like any other
tool result. Nowhere else, and never to us.browser_provide_feedback returns its report to
your AI client like any other tool result, and it tries to add one line per new
report to ~/.browser-mcp/feedback.jsonl on your machine: the time, the kind,
the tool, what the agent says happened, what it tried and what worked in the
end, the page's origin and path, version numbers, a short diagnosis, the number
of connected extensions and a fingerprint used to skip repeats. In the three
things the agent wrote (what happened, what it tried, what worked), email
addresses and numbers of six or more characters are replaced with [email] and
[number] first, in the file and in the pre-filled issue link it returns; the
page address is only cut to origin and path. The server does not submit the
report. Opening the link sends its contents to GitHub; an issue is created only
when you submit it. Delete the file to clear it.localhost, on
the same machine; the server reaches the network only for the npm version check
you can turn on with BROWSER_MCP_CHECK_NPM=1. That bridge is local and unauthenticated:
another program running as you on the same machine can connect to it. Browser
MCP does not protect you from software you already run.Full policy: https://browsermcp.dev/privacy
MIT - Agent360
The browser tool that can stop and ask you. A 2FA code, a CAPTCHA, a choice only you can make: it asks on your screen, then carries on in the same signed-in Chrome. 40 tools, MCP clients that run loca
{ "mcpServers": { "agent360dk-browser-mcp": { "command": "npx", "args": [ "-y", "@agent360/[email protected]" ] } }}ओवरव्यू
The browser tool that can stop and ask you. A 2FA code, a CAPTCHA, a choice only you can make: it asks on your screen, then carries on in the same signed-in Chrome. 40 tools, MCP clients that run local servers, MIT.
टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Browser stdio पर लोकल चलता है।
पिछली जाँच 2026-11-14 को हुई। The browser tool that can stop and ask you. A 2FA code, a CAPTCHA, a choice only you can make: it asks on your screen, then carries on in the same signed-in Chrome. 40 tools, MCP clients that run local servers, MIT.