Yolo Chrome MCP for Claude

Tracking since May 21, 2026.

Changelog

• Jun 9, 2026
  description

  Hand any open Chrome tab to Claude. Click, type, screenshot, read console — all on your already-logged-in browser session.

  Yolo Chrome MCP turns your real, logged-in Chrome session into a tool Claude can drive.
  
  ▼ IMPORTANT — this extension is one half of the system.
  After installing it, run this one command on your computer (it adds the MCP
  server to Claude and sets up routing so Claude always uses Yolo for Chrome):
  
      npx -y yolo-chrome-mcp@latest install --routing-only
  
  Requires Node.js + Claude Code (or Claude Desktop). The extension popup also
  shows this command with a one-click "Copy" button — open it any time the
  status dot is red.
  
  Pair it with the yolo-chrome-mcp server (npm or Claude Desktop) and Claude
  can browse, click, type, screenshot, and read the console / network of any
  tab you already have open — without spawning a separate headless browser,
  without re-authenticating, and without leaving your computer.
  
  It is the lowest-friction way to give Claude an "eyes and hands" on the
  exact pages you are working with.
  
  — What you can do —
  • "Take a screenshot of my Stripe dashboard and tell me what's wrong"
  • "Open Linear and triage today's issues for me"
  • "Read the console errors on this React app and find the cause"
  • "Fill out this form with my info but stop before submit"
  • "Compare the Polymarket prices across these 3 tabs"
  • "Open Gmail and summarize the last 10 unread threads"
  
  — How it works —
  1. Install this Chrome extension. It connects to a local WebSocket on
     your computer (127.0.0.1, no external traffic).
  2. Run the one-line install command shown above. It registers the MCP
     server with Claude (`claude mcp add`) and installs the routing hook
     + CLAUDE.md rule so Claude always picks Yolo when it needs a browser.
  3. Restart Claude Code / Claude Desktop. The extension popup's dot turns
     green once Claude spawns the server.
  4. Ask Claude to do something with a tab. Claude calls the server, the
     server forwards the call to this extension, the extension acts on
     your Chrome tab using DevTools Protocol, and the result comes back
     to Claude.
  
  — 19 tools, lean by default —
  listTabs · getTabInfo · screenshot · getPageText · getInteractables ·
  click · type · scroll · navigate · createTab · closeTab · evalJs ·
  waitForStable · getConsoleLogs · getNetworkActivity · getNetworkRequest
  · getStorage · getSourceAt · setSafetyMode
  
  Designed so Claude picks the cheapest tool for the job (accessibility
  tree over screenshots, filtered logs over full dumps), keeping the
  conversation context small.
  
  — Safety overlay —
  A locally-rendered confirmation banner asks before potentially-sensitive
  actions: payment / purchase labels, account deletion, password-form
  submits, credit-card / password input, and risky JavaScript that touches
  cookies / fetch / localStorage. Navigation and ordinary clicks pass
  through without prompts. Configurable via the popup.
  
  — Multi-session safe —
  Multiple concurrent Claude Code sessions on the same machine share one
  extension via a primary/secondary MCP architecture. No port conflicts,
  no "Failed to connect" surprises.
  
  — What this extension does NOT do —
  • It does not transmit data to any third-party server. Everything goes
    through 127.0.0.1 only.
  • It does not read tabs in the background without an explicit AI
    request.
  • It does not contain analytics or telemetry.
  
  — Open source —
  Source: https://github.com/rikutoe/yolo-chrome-mcp
  License: MIT
  Bugs / requests: https://github.com/rikutoe/yolo-chrome-mcp/issues
  
  Privacy policy: https://seedx.tech/privacy

Permissions & access

Permissions

tabsdebuggerstoragescriptingcookiesalarms

Host access

<all_urls>

Screenshots