Agent360 Browser MCP

Name: Agent360 Browser MCP
Author: Agent360dk

by Agent360dkversion 1.31.0i★ –iRuns on your computer

Registry nameio.github.Agent360dk/browser-mcp

Install

Overview

Description from the maker (original English)

Drive your real, logged-in Chrome from any AI agent - 40 tools. Needs our Chrome extension too.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Web & browsers

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "browser": {
      "command": "npx",
      "args": [
        "-y",
        "@agent360/browser-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add browser -- npx -y @agent360/browser-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "browser": {
      "command": "npx",
      "args": [
        "-y",
        "@agent360/browser-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "browser": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@agent360/browser-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Agent360dk, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Web & browsersi

More stars than 0% of the other 875 servers in this category
Published to the registry more recently than 80% of the other 875 servers in this category
Basic checks equal to or better than 100% of the other 875 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Agent360 Browser MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.31.0) reached the registry 8 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

by browser-use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

Computer or cloud★ 120,087MITUpdated 16 days ago

Install

Chrome DevTools MCP

by ChromeDevTools

Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.

Runs on your computer★ 54,821Apache-2.0Updated 15 days ago

Install

MCP Server Browser

by bytedance

MCP server for browser use access

Runs on your computer★ 39,550Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Browser MCP by 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 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.

→ [What it can and cannot get past](https://browsermcp.dev/docs/capability-matrix/) - every wall, marked *measured*, *by design*, *not yet*, or *won't*. Including the ones we have not fixed.

▶ [Watch the 15-second film →](https://browsermcp.dev/film.mp4)

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.

The whole thing, in four steps

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_tabs to 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.

The long version - install, step by step

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.

Step 1: Register the MCP server with Claude Code

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.)

Step 2: Load the extension in Chrome

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.

Open Chrome and type chrome://extensions in the address bar
Toggle "Developer mode" ON (top right corner)
Click "Load unpacked" (top left, next to "Pack extension")
Navigate to `~/.browser-mcp/extension/` and click "Select"

On Mac: Press Cmd+Shift+G in the file picker, paste ~/.browser-mcp/extension/, press Enter
On Windows: Paste %USERPROFILE%\.browser-mcp\extension\ in the address bar (Windows is not yet verified: our automated tests do not pass there)
On Linux: Type ~/.browser-mcp/extension/ in the path field

Restart Claude Code so it picks up the new MCP server

That's it. The Browser MCP icon will appear in your toolbar, and 40 browser tools are now available in Claude Code.

Alternative: Manual zip download (no npm)

If you don't want to use npm, download the extension directly:

Download the extension zip (agent360-browser-mcp- .zip) from the latest GitHub release
Unzip the file (anywhere - e.g. ~/Downloads/browser-mcp-extension/)
Follow Step 2 above, but select the unzipped folder instead of ~/.browser-mcp/extension/
Register the server - run 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"] } } }

Chrome Web Store (no Developer mode, auto-updating extension)

This replaces Step 2 only - you still need Step 1.

Install the extension from the Chrome Web Store → - no Developer mode toggle, and Chrome keeps it updated for you.
Register the MCP server:

   claude mcp add --scope user browser-mcp -- npx @agent360/browser-mcp@latest

(For Cursor / VS Code / Codex, use that client's own MCP config instead - see browsermcp.dev/docs.)

Restart Claude Code.

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.

You're in. Now what?

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):

Say this	What it shows
"Open example.com and take a screenshot."	Start here. An image back instead of "I don't have browser access" means both halves are talking. That is the whole install test.
"Open Gmail and tell me who sent my last 3 emails."	The one that shows the difference - it works because it is your browser, already signed in. A fresh headless browser would hit a login wall here.
"Go to my analytics dashboard, pull this month's numbers, and put them in a table."	A dashboard you are signed into in this Chrome. No API key, no export, no integration to build first.
"Fill in the signup form at example.com/signup with my details. Stop and ask me before anything sensitive."	You stay in the loop - the agent can pause and ask you before passwords, payment details, or anything it should not decide alone.
"Log me in at app.example.com. If it emails a code, open Gmail, read the code and continue."	The move that needs no email-API setup: it opens your Gmail, reads the one-time code and finishes the sign-in.
"Walk through my app's signup flow as a real user and tell me where it breaks."	End-to-end QA of your own product, in the same browser your users have.

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.

Why This Over Playwright MCP / BrowserMCP?

	Browser MCP	Playwright MCP	BrowserMCP.io
Browser	Your real Chrome, via extension	Persistent profile by default, or your Chrome via their extension	Your real Chrome
Maintained	Actively - latest release v1.31.0 (2026-10-28)	Actively (Microsoft)	Last commit Apr 2025
Logins/cookies	Your existing session	Persistent profile keeps logins between runs	Already authenticated
Several agents, one logged-in profile	20 concurrent, each with its own color-coded tab group	Also supported: their extension gives each connected client its own coloured tab group	Single session
Human-in-the-loop	`browser_ask_user` - 2FA, CAPTCHA, credential input	None: 72 documented tools, none that can ask the person (checked 2026-09-19)	None
Token-finding guides	9 built-in (Stripe, HubSpot, Slack...)	None	None
CORS bypass	`browser_fetch` from extension background	N/A	Limited
Network monitoring	`browser_wait_for_network` via CDP	Built-in	None
CSP-strict sites	Chrome Debugger API throughout	Works	Limited
Custom dropdowns	Angular Material, React Select support	Works	Limited
Install	`claude mcp add` + extension from the Chrome Web Store	`npx @playwright/mcp`	`npx @browsermcp/mcp` + Chrome Web Store

Th

Only the beginning is shown; read the rest in the repo

Say this	What it shows
"Open example.com and take a screenshot."	Start here. An image back instead of "I don't have browser access" means both halves are talking. That is the whole install test.
"Open Gmail and tell me who sent my last 3 emails."	The one that shows the difference - it works because it is your browser, already signed in. A fresh headless browser would hit a login wall here.
"Go to my analytics dashboard, pull this month's numbers, and put them in a table."	A dashboard you are signed into in this Chrome. No API key, no export, no integration to build first.
"Fill in the signup form at example.com/signup with my details. Stop and ask me before anything sensitive."	You stay in the loop - the agent can pause and ask you before passwords, payment details, or anything it should not decide alone.
"Log me in at app.example.com. If it emails a code, open Gmail, read the code and continue."	The move that needs no email-API setup: it opens your Gmail, reads the one-time code and finishes the sign-in.
"Walk through my app's signup flow as a real user and tell me where it breaks."	End-to-end QA of your own product, in the same browser your users have.

Agent360 Browser MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Web & browsersi

Common questions

Alternatives

Browser Use

Chrome DevTools MCP

MCP Server Browser

README from the maker

Browser MCP by Agent360

The whole thing, in four steps

The long version - install, step by step

Step 1: Register the MCP server with Claude Code

Step 2: Load the extension in Chrome

Alternative: Manual zip download (no npm)

Chrome Web Store (no Developer mode, auto-updating extension)

You're in. Now what?

Why This Over Playwright MCP / BrowserMCP?

Th