Skip to main content
Glama

TabDeck lets a local AI agent drive your real, logged-in Chrome over MCP, with every task kept in its own named tab group. A small Chrome extension plus a zero-dependency MCP server; works with Claude Code, Codex, Copilot CLI, Cursor or any other MCP client.

NOTE

Inspired byClaude in Chrome. TabDeck is an independent, model-agnostic take on the same idea. It is not affiliated with Anthropic and shares no code with that extension.

✨ Why

Your logged-in Chrome

No prompt per connection

Any model / client

Tidy agent tabs

Remote-debugging MCPs

✅

❌

✅

❌

Extension-relay MCPs

✅

✅

✅

⚠️

Claude in Chrome

✅

✅

❌

✅

TabDeck

✅

✅

✅

✅

  • 🗂️ One tab group per session, named after the task, in a color that stands apart.

  • 🧲 Tabs opened by a click stay in the group and never steal the tab you are looking at.

  • 🌙 Works in background tabs: clicking, typing and screenshots need no focus.

  • 🔒 Only touches its own tabs, unless it explicitly adopts one of yours.

  • 🚫 No "Open the app?" prompts: pages cannot launch desktop apps (msteams:, zoommtg:, slack:, mailto: ...), so the agent stays in the web version and nobody has to click a browser prompt.

  • 🔍 Debugging built in: console, network, dialogs, iframes and file uploads.

  • 🪶 No dependencies: about 1,700 lines of plain JavaScript.

Related MCP server: byob

🎬 Demo

Images on this page are illustrations, not captures of a real browser.

🚀 Install

Chrome 116+, Node.js 18+, Windows only for now.

git clone https://github.com/shaojunying/tabdeck.git
cd tabdeck
node scripts/setup.mjs
  1. Open chrome://extensions, turn on Developer mode, Load unpacked, choose extension/.

  2. Add the stdio server to your MCP client:

    { "mcpServers": { "tabdeck": { "command": "node", "args": ["C:\\path\\to\\tabdeck\\src\\mcp-server.js"] } } }

    Claude Code: claude mcp add tabdeck -- node C:\path\to\tabdeck\src\mcp-server.js

Uninstall with node scripts/setup.mjs --uninstall, then remove the extension.

🧰 Tools

Tool

What it does

session_start

Name this session's tab group after the task

tabs_list

List this session's tabs, or everything with scope="all"

tab_open

Open a tab in the group, in the background by default

tabs_adopt

Take over existing tabs by moving them into the group

tabs_close

Close tabs; only the session's own unless force=true

tab_activate

Switch to a tab

tabs_group / tabs_ungroup

General tab organising

group_set

Rename, recolor, collapse or expand a group

session_end

Close everything, dissolve the group, or keep it

Tool

What it does

page_navigate

Load a URL and wait for it

page_snapshot

Read the page, iframes included, as a compact accessibility tree with element refs

page_click

Click by ref; reports tabs the click opened

page_type

Type into a field by ref, optional Enter

page_key

Press a key

page_select

Choose options in a native <select>

page_fill

Fill several fields in one call: text, selects, checkboxes

page_upload

Choose local files in a file input

page_dialog

Accept or dismiss an alert, confirm or prompt

page_hover

Hover an element

page_scroll

Scroll by a screen, to top / bottom, or to an element

page_history

Back, forward, reload

page_wait

Wait for text to appear or disappear

page_eval

Run a JavaScript expression in the page

page_screenshot

JPEG of the visible area, at most 1280px wide

page_console

Console output and uncaught errors, including earlier ones

page_network

Requests the tab made; headers and bodies for one request

Tool

What it does

web_search

Search the web with no API key: opens a background tab on Google (Bing if Google shows a captcha or nothing), returns title, URL and snippet for up to 10 results, then closes the tab

🧩 How it works

flowchart LR
    A["MCP client"] -- stdio --> B["mcp-server.js<br/>one process = one session"]
    B -- named pipe --> C["host.js"]
    C -- native messaging --> D["extension"]
    D -- "tabs · tabGroups · debugger" --> E["Chrome"]

Page actions use chrome.debugger, so Chrome shows its "started debugging this browser" bar while a session is acting on a page.

🛡️ Limits and security

WARNING

The agent has the same access to a page as you, including your logins. Use it only with agents and prompts you trust; web pages can contain text written to mislead an agent.

  • Not yet: macOS / Linux, per-site allowlist, screen recording.

  • page_network only sees requests made after TabDeck first acted on the tab, and redacts cookie and authorization headers.

  • page_upload refuses files that look like credentials or keys. This is a guard against slips, not a security boundary.

  • page_eval runs arbitrary JavaScript in session tabs.

  • web_search reads the search engine's result page, so it runs as you (your region, language and account) and can break when that page's markup changes. Many searches in quick succession can trigger a captcha; npm run test:search checks it against the live sites.

  • chrome:// pages and the Chrome Web Store cannot be driven.

  • node test/plumbing.test.mjs tests the server and host without Chrome; npm run test:live runs against your real Chrome with temporary tabs.

  • node scripts/reload.mjs reloads the extension after you change extension/, with no Chrome prompt.

  • Cannot reach the TabDeck extension: Chrome is not running, the extension is not loaded, or setup has not been run.

  • Specified native messaging host not found: you ran setup from a shell inside a packaged (MSIX) app, which writes to a private registry view. Rerun it with --via-wmi.

  • Logs: native-host/host.log, and the "service worker" link on the TabDeck card in chrome://extensions.

📄 License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI agents drive the real, already-logged-in Chrome browser through a companion extension, navigating tabs, clicking, typing, reading pages, filling forms, taking screenshots, and inspecting cookies, storage, console and network traffic. It keeps all communication on the local machine, with no remote-debugging port to expose and no separate headless browser or manual cookie copying to set up.
      1 npm
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding assistants drive the user's own already-signed-in Chrome, so agents can read logged-in pages, click, fill forms, navigate, screenshot, inspect network traffic and storage, and run multi-step browser workflows without a separate headless browser or remote debugging port. All communication stays on the user's machine and agent-opened tabs are grouped so they never steal focus.
      1 npm
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI assistants drive your real, already-logged-in Chrome through a browser extension, so agents can read, click, type, navigate, screenshot, inspect network traffic, and manage cookies or storage on pages that require existing sessions. It works without opening a remote-debugging port and keeps all communication on your machine.
      1 npm
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive the user's actual, already-logged-in Chrome browser — snapshotting pages, clicking, typing, navigating, reading content, taking screenshots, and inspecting cookies, network traffic, and console output. Browser automation happens through a Chrome extension using Native Messaging, so no remote-debugging port is exposed and all communication stays on the local machine.
      1 npm
      ISC