ykdojo

Browser Bridge — AI skill for Claude Code

AI community

Browser Bridge: a Chrome extension + local MCP server that gives any AI agent access to your real, logged-in browser.

How to install Browser Bridge

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ykdojo/browser-bridge and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Browser Bridge does

Browser Bridge: a Chrome extension + local MCP server that gives any AI agent access to your real, logged-in browser.

Alternatives in AI

Design Md Chrome — Chrome extension to extract styles from any website and generate DESIGN.md files and design skills for AI base 2.7k ★
Deepseek Pp — DeepSeek Web browser extension: AI agent workspace with MCP tools, memory, Skills, automation, web search, and 1.7k ★
Openteam — A Chrome extension for orchestrating local AI-agent team workflows across web AI services 174 ★

README

Browser Bridge

A Chrome extension plus a local MCP server that lets AI agents (Antigravity, Claude Code, or any other) control your real, logged-in Chrome. You can think of it as an open source alternative to Claude for Chrome, built a slightly different way.

Everything stays local. Extension ↔ localhost WebSocket ↔ MCP server, no third-party relay, no accounts.
Any MCP client can drive it, not just one product.
The codebase is deliberately small: two files. The extension is one background script acting as a thin relay into Chrome; the MCP server is one file holding all the logic, talking to the extension over the local WebSocket.
The tool names and input shapes are kept consistent with Claude for Chrome's. The implementation is independent.

Tools that are features of the Claude product rather than browser primitives are left out: image/file upload, GIF recording, plan approval, shortcuts, window resizing. Also not replicated yet: Claude for Chrome's guardrails (site permissions, blocked categories, confirmation prompts) - see Known gaps.

How it works

extension/ - Manifest V3, thin relay. Connects to ws://127.0.0.1:17333, forwards Chrome DevTools Protocol (CDP) commands to tabs through chrome.debugger, buffers console/network events per tab, and answers JavaScript dialogs the agent triggers. Its toolbar popup shows connection status and links to a short "How it works" page. Pings every 20s to keep the service worker alive, and a chrome.alarms tick every 30s wakes it to look for a server again.
server/ - Node MCP server over stdio that also hosts the WebSocket. All logic lives here, so most changes need no extension reload. Tools: tabs_context, tabs_create, tabs_close, navigate, computer, read_page, find, form_input, get_page_text, javascript_tool, read_console_messages, read_network_requests.