Ext Ops Panel
Open dashboard
Comparison

terminal-firefox-skill vs brawsr

terminal-firefox-skill is a plugin bundle for AI coding tools published by gyoz-ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). brawsr is an MCP server published by brawsr. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceterminal-firefox-skillbrawsr
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (npm): 191
Downloads/week (npm): 33
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

terminal-firefox-skill vs brawsr
Factterminal-firefox-skillbrawsr
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@brawsr/mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/gyoz-ai/terminal-firefox-skillgithub.com/brawsr/mcp-server
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

terminal-firefox-skill

In its own words, on Claude Code: claude-plugins-community:

Full Firefox browser in your terminal for Claude Code. Launches Browsh (a terminal Firefox renderer) in a tmux split pane and controls it via Marionette protocol. Includes a one-time Firefox patch that removes the hardcoded single-session limit on Marionette, allowing the control script to create session #2 alongside Browsh. Full command set: nav, eval, click, type, html, shot, title, url, back, forward, refresh, windows. Based on the actively maintained Browsh project.

brawsr

In its own words, on Official MCP Registry:

Browser sessions, checkpoints, rewind, fork, lineage, and lifecycle tools for brawsr.

How to run each

terminal-firefox-skill As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install terminal-firefox-skill@claude-community

brawsr As a local MCP server: npm package

Claude Code
claude mcp add --env "BRAWSR_API_KEY=<YOUR_BRAWSR_API_KEY>" --transport stdio brawsr -- npx -y @brawsr/mcp-server

Requires: BRAWSR_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of terminal-firefox-skill publish no settings it asks for, so we do not compare settings.

What it can do: terminal-firefox-skill · What it can do: brawsr · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built