real-browser-control
Connect an AI coding agent to the user's REAL Chrome via Real Browser MCP (local MCP server + Chrome extension over localhost WebSocket). Use for live UI verification, already-open tabs, existing cookies/SSO/2FA, staging admin panels, and any task where headless Playwright or a cloud agentic browser would miss the human's session. Triggers: control my chrome, real browser MCP, use my logged-in browser, not headless, verify in the browser I have open, click with my SSO session, agentic browser but real Chrome, Chrome extension MCP. Skip for CI, parallel clean runs, or unattended scraping. Extension must show green connected. Prefer browser_snapshot; avoid browser_evaluate on strict-CSP sites (GitHub, Google).
