mcpbeat Sign in

Agent360 Browser MCP Server

local only

Agent360 Browser MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 1 456 installs a week from npm. Last commit 19 Sep 2026.

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

Installs per day peak 662 · avg 118 · +503% w/w
a month agotoday
1 456
Installs / week
npm · @agent360/browser-mcp
44
Stars
4 open issues
19 Sep 2026
Last commit
0 releases in 90 days
MIT
License
JavaScript

What the code does

We read the source, 6 h ago · rules 3dff92dd89df

A tool parameter reaches a dangerous call

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

A tool parameter reaches a file or shell call browser_navigate.path → mcp-server/index.js:333, browser_screenshot.path → mcp-server/index.js:620, browser_screenshot.path → mcp-server/index.js:352 и ещё 3
        writeFileSync(targetPath, Buffer.from(base64, 'base64'));
Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

File ships in the package but is absent from the source [пакет] bin/cli.js:1, [пакет] index.js:1, [пакет] tools.js:1 и ещё 1
этот файл ставится пользователю, но в репозитории его нет
const p = spawn(process.execPath, [SRV], { stdio: ['pipe', 'pipe', 'pipe'] });
            try { fn = new Function('return (' + codeStr + ')'); }

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

A tool parameter here reaches a dangerous call

That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add browser-mcp -- npx -y @agent360/browser-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "browser-mcp": {
      "args": [
        "-y",
        "@agent360/browser-mcp"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.browser-mcp]
command = "npx"
args = ["-y", "@agent360/browser-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "browser-mcp": {
      "args": [
        "-y",
        "@agent360/browser-mcp"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "browser-mcp": {
      "args": [
        "-y",
        "@agent360/browser-mcp"
      ],
      "command": "npx"
    }
  }
}

Alternatives to Agent360 Browser MCP

same job, measured the same way
I
Doppel
by samrj12

Drive your real, logged-in Chrome/Edge from AI agents over CDP. Faster. Sharper.

80 installs/wk local only
Vibe MCP — Real Chrome, Remotely
by vibetechnologies

Drive your real, logged-in Chrome from any MCP client — even from a remote machine, no inbound port.

133 installs/wk answering
Chrome Bridge
by frsorrentino

Your real, logged-in Chrome as an MCP server: 59 token-efficient web-dev tools. ChromeOS included.

261 installs/wk local only
BrowserTap MCP
by linvireo

MCP server that drives the real Chrome you already use, through an extension and CDP.

97 installs/wk local only
Chromeflow
by neodrew

Lets Claude Code or Codex CLI drive your real Chrome — sessions intact, 28 browser tools.

local only
R
Chromeflow
by chromeflow

Lets Claude Code or Codex CLI drive your real Chrome — sessions intact, 28 browser tools.

local only
Crawlio Browser
by crawlio

Bridge a live Chrome browser to your agent: 150 tools for capture, extraction, and observation.

132 installs/wk local only
Real Browser
by ofershap

MCP server + Chrome extension for AI browser control with real sessions.

83 installs/wk local only

Agent360 Browser MCP — questions

Answers built from our own checks of this server.

Why is there no uptime for Agent360 Browser MCP?
Agent360 Browser MCP runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @agent360/browser-mcp was installed 1 456 times last week.
How do I connect Agent360 Browser MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @agent360/browser-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Agent360 Browser MCP?
The npm package @agent360/browser-mcp was installed 1 456 times in the last week. Week over week that is +503%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Agent360 Browser MCP open source?
Yes — it is published under the MIT licence, written in JavaScript, 44 stars on GitHub and 4 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.