概述
让 MCP 客户端(Claude Code、Codex 等)操作你真实的 Chrome —— 你的标签页与登录状态。新站点和高危操作需要你授权。
Browser Bridge lets any MCP client — Claude Code, Claude Desktop, Codex, or anything that speaks the Model Context Protocol — drive YOUR real Chrome: your tabs, your logged-in sessions, your cookies. No second browser, no CDP debug port, no --remote-debugging flag. Because it operates the browser you're already signed into, an AI agent can do things a fresh headless browser can't: read a page behind your auth, click through an app you're logged into, or inspect what your app stashed in localStorage. That power is also the risk, so Browser Bridge is built around explicit consent: • Approve every site. A new origin triggers a popup prompt — nothing runs on a site you haven't approved. • Confirm high-risk actions. Submit clicks, link navigations, tab close, and every JavaScript evaluation pop an on-page confirmation you must approve. • Read-only credentials. Cookies and web storage can be read (always masked), never written — there is no cookie/storage write API by design. • Authenticated local bridge. The extension talks to a localhost native host authenticated with a per-run secret; nothing is sent to any remote server. HOW IT WORKS This extension is one half of Browser Bridge. It connects, via Chrome native messaging, to a small local host binary you install separately. Your MCP client connects to that host. All communication stays on your machine (localhost). REQUIRES a separate one-time install of the native host binary. See the setup guide: https://github.com/whg517/browser-bridge Open source (project link below). No analytics, no tracking, no remote code.
详情
- 版本0.5.0
- 上次更新日期2026年8月1日
- 大小50.48KiB
- 语言2 种语言
- 开发者
邮箱
huagang517@gmail.com - 非交易者该开发者尚未将自己标识为交易者。欧盟地区消费者须知：消费者权利可能不适用于您与该开发者达成的合约。
隐私权
该开发者已声明，您的数据：
- 不会因未获批准的用途出售给第三方
- 不会为实现与产品核心功能无关的目的而使用或转移
- 不会为确定信用度或放贷目的而使用或转移
支持
若有任何疑问、建议或问题，请访问开发者的支持网站
