Skip to main content
Glama

Tabherd

Your browser, connected to your agent. A thin extension and local native bridge expose browser APIs through six MCP tools and a JSON CLI. Organize tabs, move windows, save bookmarks, read pages, and interact with the browser you already use.

Quick start

Requires Node.js 22.18 or newer.

npm install -g tabherd
  1. Download tabherd-VERSION-chrome.zip from the latest release and unzip it. Load the folder as an unpacked extension in Chrome, Chromium, Edge, or Brave (Developer mode → Load unpacked).

  2. Register the host for every installed browser: tabherd setup.

  3. Reload the extension and check its popup connection.

  4. Run tabherd doctor, then tabherd call tabs.query '[{}]'.

For Firefox, download tabherd-VERSION-firefox.zip and temporarily load its manifest.json from about:debugging.

On Nix, nix run github:lmdevv/tabherd -- --help runs the CLI. The NixOS and Home Manager modules (programs.tabherd.enable = true) register the browsers declaratively, so you skip tabherd setup. See Nix and NixOS.

Add the bridge to your agent’s stdio MCP configuration:

{
  "mcpServers": {
    "tabherd": {
      "command": "tabherd",
      "args": ["mcp"]
    }
  }
}

The browser starts the native host automatically. No account or separate server. Tabherd grants local control of your real browser profile; use it with agents you trust, and pick Full access, Standard (no cookies, page JavaScript, or data deletion) or Read only in the extension popup. API availability varies by browser.

Quick start · Nix and NixOS · Tools and CLI · Agent skill

Related MCP server: browserpilot-mcp

From source

Requires pnpm.

pnpm install
pnpm build

Load apps/extension/dist/chrome-mv3 as an unpacked extension, then use node packages/bridge/dist/index.js in place of tabherd. Firefox: pnpm build:firefox, then load apps/extension/dist/firefox-mv2/manifest.json.

Docs: pnpm --filter docs dev. Checks: pnpm test and pnpm check-types. Optional real browser test on Linux with Chromium: pnpm test:browser.

License

MIT

Maintenance

ActivityMaintained
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    MCP server for local browser control via Chrome/Edge extension, enabling agents to open isolated tabs, observe pages, take screenshots, and interact with accessible controls using an existing browser profile. It is agent-agnostic, local-only, and supports safe session scoping with origin grants and sensitive-data blocking.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables remote AI agents to control a local, authenticated desktop browser over MCP through an outbound WebSocket bridge and Chrome extension, supporting tab management, navigation, page reading, clicking, typing, scrolling, screenshots, and JavaScript evaluation.
    1
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents to see and control the user's real Chrome/Brave/Edge profile over MCP, so they can read pages, click, type, take screenshots, audit layouts, debug CSS, and scrape paginated or infinite-scroll data. Because it drives the normal browser via the DevTools protocol with real input events, it works on modern JavaScript apps and on sites where the user is logged in.
    12 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables an AI agent to read and operate the Chrome or Edge tabs you are already using — titles, URLs, text, HTML, screenshots, clicks, typing, scrolling, and tab management — via a browser extension and native messaging, without restarting the browser, switching profiles, or opening a debug port. It exposes these capabilities as 19 MCP tools, with access limited to explicitly shared tabs and hardened by per-tab, origin-bound grants plus domain allow/deny lists.
    1
    MIT