Browser Use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Description from the maker (original English)
Let your coding agents use your real, signed-in Chrome, in background tabs that never steal focus.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"tabhand": {
"command": "npx",
"args": [
"-y",
"tabhand",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add tabhand -- npx -y tabhand mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"tabhand": {
"command": "npx",
"args": [
"-y",
"tabhand",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"tabhand": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"tabhand",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain tabhand.dev (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.10.1) reached the registry 15 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
MCP server for browser use access
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Tabhand
Let your AI agents use your own Chrome, signed in to your accounts,
in background tabs that never steal your focus.
tabhand.dev · Docs · Chrome Web Store
https://github.com/user-attachments/assets/d5fe5c5a-c012-471f-bf3b-10fa754c382d
Video not playing? Watch it on tabhand.dev
npx tabhand setup
Works with Claude Code, Codex, Cursor, OpenCode, Gemini CLI, Copilot and more: 19 agents in all, plus anything else that speaks MCP.
Then add the extension from the Chrome Web Store. Setup opens the page for you. It works in Brave, Edge and Dia too.
agent ──stdio──▶ tabhand mcp ──Unix socket──▶ native host ──native messaging──▶ extension ──chrome.debugger──▶ agent's tabs
active: false, inside a tab group named after the agent. Focus emulation keeps those tabs rendering, so clicks, typing and screenshots work without bringing anything to the front. Agent tabs are muted, and the agent moves on once a page is usable instead of waiting for every video to load.tabhand cursor --name Acme --color '#FF5A1F' --icon initial.npx tabhand setup
That's all:
~/.tabhand and connects it to Chrome, and to Brave, Edge and Dia (macOS) if you have them.mcp add command, setup uses it. Otherwise it edits the agent's settings file in place, keeping comments, and backs up the original to ~/.tabhand/backups.Agents it knows:
To add it to only some of them, run npx tabhand setup --harness claude,codex.
Using Brave, Edge or Dia? Add the extension there from the same Chrome Web Store page. Edge asks you to allow extensions from other stores first. Each browser shows up to agents as one more profile: click the Tabhand icon in it and give it a name, such as "Brave", so agents can ask for it. Arc isn't supported: tab groups and screenshots never finish there, so Tabhand stays out of Arc even if you add the extension. Arc shuts down on December 22, 2026; Dia works.
tabhand status checks the install, the Chrome connection and each agent. tabhand remove undoes it all. Run npx tabhand@latest setup again to update.
Any other MCP client can run ~/.tabhand/bin/tabhand mcp itself (on Windows, %USERPROFILE%\.tabhand\bin\tabhand.cmd mcp).
winget install OpenJS.NodeJS.LTS.npx says running scripts is disabled on this system, run npx.cmd tabhand setup instead, or use Command Prompt.HKEY_CURRENT_USER in the registry. Nothing needs an administrator.npm install
node bin/tabhand.mjs setup # builds dist/tabhand.mjs and installs it from this checkout node bin/tabhand.mjs reload # after changing the extension's code
From a checkout, setup has you load the extension unpacked (Developer mode, then "Load unpacked") instead of adding it from the Chrome Web Store.
Setup copies a single bundled file (dist/tabhand.mjs, built by npm run build), because macOS doesn't let Chrome's child processes read Documents, Desktop or Downloads. Agents and Chrome both start it through ~/.tabhand/bin/tabhand. That launcher remembers which Node.js ran setup, since agent apps don't get your shell's PATH. If that Node.js is removed later, it finds another one. If Chrome never connects, the bridge's log at ~/Library/Application Support/tabhand/host.log says why.
On Windows, Chrome starts the bridge through ~\.tabhand\bin\tabhand-host.cmd, which the registry points it to, and agents run the Node.js that ran setup with ~\.tabhand\app\tabhand.mjs directly, since they start programs without a shell. The log is in %LOCALAPPDATA%\tabhand\host.log, and anything the bridge printed while failing to start is in host-errors.log next to it.
Windows-only code lives in src/windows.mjs and extension/windows.js. The shared files call into them only behind a Windows check, and keep their macOS code as it is.
| Tool | What it does |
|---|---|
browser_open_tab | Open a background tab in the agent's tab group, optionally loading a URL, in the Chrome profile it asks for |
browser_navigate | Load a URL in one of the session's tabs |
browser_snapshot | Read the page as an accessibility outline; actionable elements, including ones a page made clickable or draggable out of plain elements, get refs like e123 |
browser_click | Click an element by ref, or by the text it shows |
browser_hover | Move the pointer over an element (by ref or text) to reveal controls that only show on hover, and get a fresh snapshot with refs for them |
browser_drag | Drag one element onto another, by ref or text: reorder lists, move cards between columns. Works with the browser's own drag and drop and with pages that follow the mouse |
browser_type | Type into a field, optionally clearing it first and pressing Enter after, or choose a dropdown option by its text |
browser_press_key | Press a key or combination such as Shift+Tab |
browser_scroll | Scroll up or down |
browser_upload_file | Attach files from your computer to a file field, or through the button that opens a file picker (no system dialog appears) |
browser_handle_dialog | Accept or dismiss a confirm or prompt dialog the page opened (alerts are closed for you) |
browser_screenshot | Screenshot a tab, even in the background |
browser_list_tabs | List the session's tabs, in every Chrome profile |
browser_list_profiles | List the Chrome profiles that have Tabhand, by name, and whether each is on or paused |
browser_close_tab | Close one of the session's tabs |
npm test runs all of these except the smoke test.node test/setup.mjs runs setup, status and remove in a throwaway home folder holding existing agent configs. It checks that Tabhand gets added, that comments and other settings survive, that a second run changes nothing, and that the launcher serves the MCP server.node test/setup-windows.mjs does the same on Windows, with thOnly the beginning is shown; read the rest in the repo