From browser-bridge
Control the user's real Chrome browser via Browser Bridge MCP. Use when automating Chrome, testing web apps in the user's actual browser session, interacting with logged-in pages, taking screenshots, running CDP commands, or when browser-bridge MCP tools are available. Triggers on "my chrome", "my browser tabs", "control chrome", "browser bridge". Do NOT use for headless scraping of arbitrary public sites — prefer firecrawl for that.
How this skill is triggered — by the user, by Claude, or both
Slash command
/browser-bridge:browser-bridgeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Connects to the user's **running Chrome** via a local extension + MCP bridge. Unlike headless automation, this uses their real profile — tabs, cookies, logins, and extensions.
Connects to the user's running Chrome via a local extension + MCP bridge. Unlike headless automation, this uses their real profile — tabs, cookies, logins, and extensions.
Tools are exposed directly (e.g. list_tabs, navigate, click, screenshot, cdp_command).
Run /browser-bridge-setup once after install. Quick check:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/setup-wizard.sh --check
Need extensionAuthenticated: true before tools work.
bridge_status — confirm readylist_tabs — see open tabsactivate_tab or create_tab — pick contexttake_snapshot or query_elements — understand pageclick, fill, press_key, scroll — interactscreenshot or execute_script — capture or run JS| Category | Tools |
|---|---|
| Bridge | bridge_status, bridge_logs |
| Tabs | list_tabs, get_tab, create_tab, close_tab, activate_tab, navigate, reload_tab |
| DOM | take_snapshot, query_elements, click, fill, press_key, scroll, hover |
| Advanced | cdp_command, execute_script, screenshot |
| Data | get_cookies, set_cookie, remove_cookie, read_clipboard, write_clipboard, get_console_logs |
| Utility | batch_inspect, manage_extension, find_overlay, click_overlay |
| Task | Use |
|---|---|
| Page user already has open (logged in) | Browser Bridge |
| User's real Chrome session | Browser Bridge |
| Scrape arbitrary public URLs | Firecrawl |
| Helium-specific browser | helium-browser plugin |
All traffic stays on 127.0.0.1. The auth token never leaves the machine. Chrome shows a debugger banner when CDP attaches — tell the user this is normal.
npx claudepluginhub awfixers-stuff/plugins --plugin browser-bridgeSets up isolated workspaces using native worktree tools or git worktree fallback. Use before starting feature work to protect the current branch.