BrowserPlug

Browser extension that exposes data and functions to MCP clients via WebSocket

BrowserPlug lets an AI tool that speaks the Model Context Protocol (MCP), such as Claude Code, Cursor, GitHub Copilot or Codex, use the Chrome browser you already have open. Because it drives your real profile, a page that needs a login just works: the tool sees what you see. BrowserPlug has two parts. This extension is one. The other is the BrowserPlug server, a small Python program that runs on your own computer; the extension does nothing without it. Setup steps are in the README: https://github.com/MarcinWolnyEU/BrowserPlug What your MCP client can do, through nine tools: - list, open, close and switch tabs and windows - navigate and wait for the page to settle - read a page as Markdown, plain text or HTML - take a structured snapshot of a page, then click, type, fill forms, scroll and press keys - run JavaScript in a page - take screenshots of a tab, a region or a whole page - record the network requests a page makes - report connection diagnostics You can connect several browsers to one server at the same time, in any mix of Chrome, Edge, Brave, or other browsers and each MCP client chooses which one it drives. Privacy: there is no BrowserPlug account and no BrowserPlug service, so there is nowhere for your data to go except your own machine. Page data travels from the extension to the server over an encrypted WebSocket on localhost, and from there to the MCP client you connected. What that client does with it is governed by its own privacy policy. The extension makes a few requests of its own (usage percentages from claude.ai, chatgpt.com and github.com, readable model names from models.dev, and a reachability check through check-host.net, 4.ident.me and 4.tnedi.me for the network diagnostics panel); the ones that use your logged-in session can be switched off in Options. The full list is in the privacy policy. BrowserPlug gives an AI tool access to your real browser. Connect only clients you trust, and consider a separate browser profile if you do not want your everyday browsing exposed. Running JavaScript in a page needs the "Allow user scripts" switch on the extension's details page (chrome://extensions). Only you can turn it on; without it the other tools work and this one says why it is unavailable. Proxy: an MCP client can switch the whole browser to a SOCKS5 proxy (for example to reach Tor .onion sites). Nothing happens until you press "Allow the browser-wide proxy" in the popup. The client is told when it switches, and BrowserPlug switches it off by itself when it loses its connection. BrowserPlug is open source under the MIT License.