Tab Hammer

io.github.BoltCreativePublished by GitHub account BoltCreativev0.1.0Updated Nov 7, 2026

List, group, move, focus, open, and close browser tabs through the Tab Hammer extension.

VerifiedSTDIODesktop onlyBrowser Automation

Server details

Identifier: io.github.BoltCreative/tab-hammer
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Nov 7, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account BoltCreative for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.BoltCreative%2Ftab-hammer.svg)](https://sourceweft.com/mcp/io.github.BoltCreative%2Ftab-hammer?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an AI assistant list, group, move, focus, open and close browser tabs through the Tab Hammer browser extension.

What you can do: List and inspect open browser tabs
Group, move and focus tabs
Open new tabs and close existing ones
Install, diagnose and uninstall the native messaging host and agent configs via CLI commands
When to use it: Useful when you want an assistant to tidy up, organize or navigate a crowded browser session, or to open and close tabs as part of a workflow, on a desktop machine with a Chromium-based browser.
Requirements: Runs as a local process via npx, requiring Node.js 20 or newer. Needs the Tab Hammer browser extension installed in a Chromium browser (Chrome, Chromium, Brave, Edge, Arc and similar) and a desktop OS (macOS, Linux or Windows). Setup is done with the install command, followed by reloading the extension and restarting the agent.

Before you install

Install registers a native messaging host with detected browsers and writes MCP config for detected agents, copying files into a per-user directory; uninstall reverses this. The server can open and close tabs, which changes browser state. It communicates over a local socket between browser and server, so it is desktop-only and not usable from a web client.

Installation

In SourceWeft

Open Tab Hammer in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

tab-hammer-mcp

An MCP server that lets AI agents list, group, move, focus, open, and close browser tabs through the Tab Hammer browser extension.

With the extension installed, run (Node 20 or newer):

It registers Tab Hammer's native messaging host with every Chromium browser it finds (Chrome, Chrome Beta/Dev/Canary, Chromium, Brave, Edge, Arc) and this server with every agent it finds (Claude Code, Claude Desktop, Codex, Cursor, VS Code, Windsurf, Devin Desktop), on macOS, Linux, and Windows. For any other agent it prints the config to paste. Then reload Tab Hammer in the browser and restart the agent.

npx tab-hammer-mcp doctor checks each browser's registration, whether the extension is connected, and each agent's config, and says how to fix what's wrong. It also says when a newer version is out: install copies the server, so update with npx tab-hammer-mcp@latest install.
npx tab-hammer-mcp uninstall undoes exactly what install did.
--only <ids> / --skip <ids> limit either command to some targets (--help lists them).
--extension-id <id> also allows another build of the extension.
npx tab-hammer-mcp with no command runs the server over stdio.

The browser runs the host, which relays between the extension and this server over a local socket (a per-user named pipe on Windows). Both are copied to ~/.tab-hammer/mcp (%LOCALAPPDATA%\TabHammer\mcp on Windows) and run with the node you installed with.

Source: packages/mcp/README.md at commit 6fd62dd

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.0LatestNov 7, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts