Browser Bridge (MCP) v0.2.7

Exposes VS Code's integrated browser tools (the ones Copilot agent mode uses) to
external MCP agents — Claude Code, Codex CLI, or any MCP client — with a local VS Code
window or a Remote-SSH window where the agents run on the remote server.

Install

1. Download vscode-browser-bridge-0.2.7.vsix below. For Remote-SSH, install it on the
   remote (where the agents run):

   code --install-extension vscode-browser-bridge-0.2.7.vsix

2. Reload VS Code. A Browser MCP :<port> item appears in the status bar; click it to
   copy ready-to-paste agent configs (the path is resolved for your machine).
3. Register the bridge with your agent using the version-independent path
   <globalStorage>/theozhao.vscode-browser-bridge/stdio-bridge.mjs. For Codex, also add
   env_vars = ["VSCODE_BROWSER_BRIDGE_INSTANCE"].

Requires VS Code 1.110+ with the integrated browser, and the
workbench.browser.enableChatTools setting enabled.

Highlights

• 10 integrated-browser tools mirrored over MCP via vscode.lm.invokeTool, plus
  save_page_screenshot which writes image bytes straight to disk.
• Streamable-HTTP MCP server on 127.0.0.1 with bearer-token auth, and a zero-dependency
  stdio bridge that survives window reloads.
• Per-window routing: terminals carry VSCODE_BROWSER_BRIDGE_INSTANCE, so each agent
  drives the window it was launched from; agents outside a VS Code terminal stay idle
  unless they opt in with --discover/--workspace/--url.
• The stdio bridge is published to a version-independent globalStorage path, so agent
  configs keep working across extension upgrades.