Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Tabhand

by tabhandversion 0.10.1i★ –iRuns on your computer
Registry namedev.tabhand/tabhand

Install

Overview

Description from the maker (original English)

Let your coding agents use your real, signed-in Chrome, in background tabs that never steal focus.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Web & browsers

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

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 mcp

Open in Cursor

Or copy the settings yourself

Paste 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.

Open in VS Code

Or copy the settings yourself

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.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain tabhand.dev (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Web & browsersi

  • More stars than 0% of the other 876 servers in this category
  • Published to the registry more recently than 70% of the other 876 servers in this category
  • Basic checks equal to or better than 100% of the other 876 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Tabhand safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.10.1) reached the registry 15 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser

Alternatives

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

Browser Use

by 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.

Computer or cloud★ 120,087MITUpdated 16 days ago
Install

Chrome DevTools MCP

by ChromeDevTools

Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.

Runs on your computer★ 54,821Apache-2.0Updated 15 days ago
Install

MCP Server Browser

by bytedance

MCP server for browser use access

Runs on your computer★ 39,550Apache-2.0Updated 14 months ago
Install

README from the maker

Open the README

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.

Why Tabhand

  • Your logins, not a blank browser. Agents work in the Chrome you already use, so email, dashboards and admin panels just work. You never hand over a password.
  • You keep working. Every agent gets tabs of its own in the background, grouped under its name and muted. Chrome never jumps to the front.
  • Your tabs stay yours. An agent can only reach the tabs it opened, never yours and never another agent's.
  • You can watch. Each agent has its own cursor that glides, clicks and types, and its tabs wear its icon. The Tabhand button in Chrome's toolbar shows who's working and pauses every agent at once.
  • No servers. Tabhand runs entirely on your computer, with no analytics. Pages only go to the agent you're running. Read the privacy policy.

How it works

agent ──stdio──▶ tabhand mcp ──Unix socket──▶ native host ──native messaging──▶ extension ──chrome.debugger──▶ agent's tabs
  • Background by default. Each agent session opens its own tabs with 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.
  • Agents stay in their lane. The extension only lets a session reach tabs that session opened, plus any tabs and popups those pages open. Your tabs, and other agents' tabs, are invisible to it.
  • Gets along with password managers. Chrome won't let Tabhand control a page while it shows another extension's frame, such as iCloud Passwords' autofill menu. Tabhand takes those frames out of agent tabs and carries on with the step it was on.
  • No network port. The bridge talks over a Unix socket in a directory only you can read, with a fresh token each run. Web pages and other machines can't reach it.
  • Nothing sensitive logged, no telemetry. The bridge logs connect and disconnect events only: no URLs, page content or typed text.
  • You can watch. While an agent works in a tab, its cursor sits on the page, even across page loads. It glides to whatever the agent clicks, ripples on each click, shows typing dots while it types, waves when you switch to the tab, and fades out once the agent is done. It only animates while you're looking, and it's hidden from the agent's own screenshots.
  • Agent tabs stand out. While an agent works in a tab, the tab's icon becomes the agent's arrow. The site's own icon comes back when the agent is done.
  • Each agent wears its own colors, or yours. Claude, Codex, OpenCode, Cursor, Gemini and Copilot each get their own cursor and tab group color; anything else gets a violet cursor with its own name. To give every agent your team's name, color and icon instead, click the Tabhand icon in Chrome's toolbar, then the gear, and choose Custom. The tag's icon can be the name's first letter, one of ten marks, or none, in white or black to suit the color. To set it for every agent on the computer, run tabhand cursor --name Acme --color '#FF5A1F' --icon initial.
  • Stop button. Click the Tabhand icon in Chrome's toolbar and press Pause every agent, or click Cancel on Chrome's "started debugging" bar. Either pauses every agent at once.
  • Several Chrome profiles. If Tabhand is in more than one profile (say, work and personal), agents see each one and can ask for it: "use my Work profile". Click the Tabhand icon in a profile, then its name at the top of the panel, to give it a name agents know it by, or fill in that profile's Google email. Without a choice, agents use the profile that connected first. Pause Tabhand in one profile and new work goes to a profile where it's on. An agent that asked for a profile stays in it: if you pause that one, the agent hears so rather than signing in somewhere else.

Setup (macOS and Windows)

npx tabhand setup

That's all:

  • It installs Tabhand in ~/.tabhand and connects it to Chrome, and to Brave, Edge and Dia (macOS) if you have them.
  • It adds Tabhand to every agent it finds, for all your projects. Each new session gets the browser tools, and the server's instructions tell the agent when to reach for them.
  • It asks before changing anything. Where an agent has its own 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.
  • It opens Tabhand in the Chrome Web Store, so you can add the extension (once), and waits for Chrome to connect.

Agents it knows:

  • Claude Code, Codex, OpenCode, Cursor, Gemini CLI, Qwen Code, VS Code (Copilot), Copilot CLI, Kiro, Amp, Factory Droid, Warp, Junie, Antigravity
  • Devin Desktop (Windsurf), Claude Desktop, Cline, Zed

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).

On Windows
  • You need Node.js 20 or later, from nodejs.org or winget install OpenJS.NodeJS.LTS.
  • In PowerShell, if npx says running scripts is disabled on this system, run npx.cmd tabhand setup instead, or use Command Prompt.
  • Setup registers Tabhand with Chrome and Edge (Edge comes with Windows), and with Brave if you have it, under HKEY_CURRENT_USER in the registry. Nothing needs an administrator.
  • Agents reach the bridge over a named pipe, not a network port, and each has to show a token kept in your own AppData, new each time Chrome starts the bridge.
  • Tested on Windows 11 with Chrome, and with Claude Code as the agent.
Working on Tabhand
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.

Tools

ToolWhat it does
browser_open_tabOpen a background tab in the agent's tab group, optionally loading a URL, in the Chrome profile it asks for
browser_navigateLoad a URL in one of the session's tabs
browser_snapshotRead 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_clickClick an element by ref, or by the text it shows
browser_hoverMove 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_dragDrag 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_typeType into a field, optionally clearing it first and pressing Enter after, or choose a dropdown option by its text
browser_press_keyPress a key or combination such as Shift+Tab
browser_scrollScroll up or down
browser_upload_fileAttach files from your computer to a file field, or through the button that opens a file picker (no system dialog appears)
browser_handle_dialogAccept or dismiss a confirm or prompt dialog the page opened (alerts are closed for you)
browser_screenshotScreenshot a tab, even in the background
browser_list_tabsList the session's tabs, in every Chrome profile
browser_list_profilesList the Chrome profiles that have Tabhand, by name, and whether each is on or paused
browser_close_tabClose one of the session's tabs

Tests

  • 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 th

Only the beginning is shown; read the rest in the repo

Ask PopNx