Browser Hands
Give your AI agent hands in your own browser: Chrome extension + local MCP server. Logged-in, parallel, low CPU.
A fast, local Chrome MCP server for AI agents. Your browser, your logins, near-zero overhead.
Browser Hands is a Chrome extension plus a small local MCP (Model Context Protocol) server. It lets any MCP-capable agent (Claude Code, Codex, Cursor and others) drive the Chrome you already use: click, type, read pages, take screenshots, run JavaScript and record GIFs, without a cloud VM or a headless browser.
In one sentence: if you want Claude Code, Cursor, Codex or another MCP client to control your existing Chrome (your tabs, your cookies, your logged-in accounts) instead of a fresh headless browser, this is what Browser Hands does. It is free and open source (MIT).
Jump to: Quick start · Problems it solves · What people use it for · When the obvious tool gets in the way · What it does not do · Troubleshooting · FAQ
An agent filling in a Product Hunt launch form in my own logged-in Chrome (sped up, idle waits removed). MP4
Demo 1: Bulk work in one shot. An agent learns one form, then injects a script to submit it across many sites, stopping before every final submit.
Demo 2: Parallel agents, multiple profiles. Several agents work at once in their own tab groups, across two Chrome profiles (work and personal), with no cross-talk.
Demo 3: Screenshots that don't melt your laptop. Continuous screenshots next to Activity Monitor. Chrome scales the image itself; no in-page canvas re-encoding.
Why Browser Hands
Most browser automation for agents means a cloud VM, a heavy headless browser, or an extension that eats your CPU and takes over your session.
- Local only. No cloud, no accounts, no sidebar chat, no per-site permission popups. Your agent talks to your Chrome through a local process.
- Familiar tool interface. 16 of the 26 tools use the same names and arguments as the browser tools agents already know from Claude in Chrome, so existing prompts mostly carry over. The other 10 are Browser Hands additions.
- Small footprint. Screenshots are scaled by Chrome itself through the DevTools Protocol. No in-page canvas work, no animated overlays.
Problems it solves
These are the complaints we see most often in GitHub issues, Reddit and Hacker News threads about AI browser tools. Each row says what Browser Hands does about it.
Connection and accounts
From the project's README.
