Privacy Policy

Last updated: September 11, 2026

Browser MCP is an open source Chrome extension + MCP server by Agent360. We take your privacy seriously.

Data Collection

Browser MCP does not send any personal data to Agent360 or to anyone else. Specifically:

• No browsing history is collected or sent anywhere
• No cookies or login credentials are read by our servers
• No analytics, tracking, or telemetry is included
• Nothing is sent to Agent360 - there is no server of ours to receive it
• The extension keeps a short log on your own machine of which tools ran (time, tool name and session), shown in its popup. From version 1.29.1 it does not keep what the agent typed, cookie values or page addresses, and clears those from older entries when it updates. You can empty the log from the popup

How Browser MCP Works

Browser MCP runs on your own machine:

• The Chrome extension communicates with a local MCP server via WebSocket (localhost only)
• The MCP server communicates with Claude Code (or other MCP clients) via stdio
• Browser MCP itself contacts no server of ours or any third party. What does leave your machine: the pages your agent reads go to your AI client and on to its model provider; the browser visits the sites your agent opens; and npx @agent360/browser-mcp@latest looks the package up on npm once when the server starts

The localhost WebSocket bridge is not password-protected - it trusts connections from your own machine. That means the extension is only as private as your computer: any software already running on it could, in principle, connect to the same local port. Browser MCP never exposes this bridge beyond localhost, and the bridge itself sends nothing off your machine. If you share your computer with untrusted software, disable or remove the extension when you are not using it.

Permissions

Browser MCP requests the following Chrome permissions. Each is required for browser automation functionality:

• tabs, tabGroups, activeTab - See and switch between the session's own tabs, and group them by colour. The agent acts only on tabs the session opened, never on a tab you opened yourself
• cookies - Read and write cookies for browser_get_cookies / browser_set_cookies, and only for the http(s) sites the session has open
• scripting - Execute JavaScript in page context for content reading and interaction
• debugger - Chrome DevTools Protocol for reliable mouse and keyboard events, screenshots, running scripts on CSP-strict sites, and reading network responses for browser_wait_for_network
• webNavigation - List a page's frames, so a tool can reach into an iframe
• storage, alarms, offscreen - Local extension state, two timers (one keeps the bridge alive, one releases a port when a session's last tab closes), and the offscreen document that hosts the WebSocket bridge
• notifications - Alert you when a human-in-the-loop action is needed
• <all_urls> (host permission) - Browser automation requires access to whatever website you navigate to

Open Source

Browser MCP is fully open source under the MIT License. You can inspect all code at github.com/Agent360dk/browser-mcp.

Contact

Questions? Email [email protected] or open an issue on GitHub.

← Back to browsermcp.dev