Docs
Uninstall, and what it touches
Short answer: removing Browser MCP is two steps - delete the Chrome extension and drop the MCP server from your client's config. And the question behind the question - "what did it have access to?" - has a short answer too: the extension holds broad Chrome permissions because driving your real browser requires them, but it runs on your own machine and sends nothing to Agent360. There is no account, no server of ours, and no telemetry. Uninstalling leaves nothing behind on our side because there was never anything on our side.
Uninstall in two steps
- Remove the Chrome extension. Open
chrome://extensions, find Browser MCP, and click Remove. If you loaded it unpacked, delete the extension folder too. - Remove the MCP server from your client. Delete the
browser-mcpentry from your MCP config (e.g.claude mcp remove browser-mcp, or delete the block from your Cursor/VS Code/Codex config). If you installed globally,npm uninstall -g @agent360/browser-mcp.
Then delete ~/.browser-mcp/ too: it holds a local log of problems your agent reported and, for an unpacked install, the extension files. There is no uninstaller to run, no account to close, and no data of yours on any server to delete.
Checking it is really gone
You: Open example.com and take a screenshot. Claude: I don't have browser access.
That answer is what a clean uninstall looks like. If you still get an image back, the MCP server is still registered with your client - step 2 above.
Exactly what the extension can access - and why
Browser MCP requests broad permissions for one reason: its whole job is to operate the real, logged-in Chrome you already use. A tool that drives your browser needs the same reach you have. Here is the full list from the extension manifest, with what each is for:
| Permission | Why it's needed |
|---|---|
tabs, tabGroups, activeTab | See and switch between your tabs; group concurrent sessions |
scripting, debugger | Click, type, read pages, run scripts and read network responses via trusted events (works on React/Angular and CSP-strict sites) |
cookies | Read and set cookies when you ask the agent to (browser_get_cookies, browser_set_cookies). Staying logged in does not need it: Chrome sends your cookies with every page the agent opens |
webNavigation | List a page's frames, so a tool can reach into an iframe |
storage, alarms, offscreen, notifications | Local extension state, two timers (keep the bridge alive; release a port when a session's last tab closes), the WebSocket bridge, and status prompts |
<all_urls> (host access) | So the agent can work on whatever site you point it at - not a fixed list |
This is a lot of access, and we won't pretend otherwise. It is the same access any tool would need to do what this one does. What makes it safe is not a short permission list - it's where the data goes.
The one thing that matters: nothing is sent to us
The extension talks to a local MCP server over a 127.0.0.1 WebSocket bridge, and that server talks to your MCP client on the same machine. There is no Agent360 backend in the loop. Your pages, cookies, sessions and keystrokes are never sent to us - there is nowhere for them to be sent, because we don't run a server that receives them. The project is open source (MIT), so this isn't a promise you have to take on trust: you can read extension/background.js and confirm there is no outbound telemetry.
What does leave your machine is what you would expect from any AI agent: the pages your agent reads are handed to your AI client (Claude Code, Cursor, Codex...), which sends them to its model provider the same way it sends anything else you show it. The browser visits the sites your agent opens. And if you start the server with npx ...@latest, npm looks the package up once at startup.
FAQ
Does uninstalling delete my data from your servers? There's nothing to delete - Browser MCP has no account and no server that stores your data. Removing the extension, the config entry and the ~/.browser-mcp/ folder removes Browser MCP; npx also keeps a cached copy of the package under ~/.npm/_npx/, which you can delete too. If you ran npx @agent360/browser-mcp install, remove browser-mcp from every client it registered with (Claude Code, Codex, VS Code, Cursor).
Why does it need access to all sites and my cookies? Because it drives your logged-in browser on whatever site you choose; <all_urls> is so you're not limited to a pre-approved list. The cookies permission is for the two cookie tools - staying logged in works without it, because Chrome sends your cookies itself. Nothing is sent to us.
Is the debugger permission dangerous? It's what lets the agent send trusted clicks and reads that work on strict sites. Chrome shows its standard "Agent360 Browser MCP" started debugging this browser banner while a session is active; it clears when the session ends.
Can I verify the "nothing is sent to you" claim myself? Yes - it's MIT-licensed open source. Read extension/background.js and mcp-server/index.js; there is no outbound analytics or telemetry endpoint.