Ext Ops Panel
Open dashboard
Comparison

vibesurfer vs vibatchium

vibesurfer is a plugin bundle for AI coding tools published by frane. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). vibatchium is an MCP server published by trueoriginlabs. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
Marketplacevibesurfervibatchium
Claude Code: claude-plugins-community Listed
Version: 0.2.0
Forks (GitHub): 0
Stars (GitHub): 16
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.20.0
Downloads/month (PyPI): 548
Downloads/week (PyPI): 262
Forks (GitHub): 1
Stars (GitHub): 7
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

vibesurfer vs vibatchium
Factvibesurfervibatchium
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)16 (better)7 (worse)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (vibatchium)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)32
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/frane/vibesurfergithub.com/trueoriginlabs/vibatchium
Changes in the last 7 days (differs)02
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

vibesurfer

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

A real browser for your local AI agent. Native WebKit on macOS, WebKitGTK on Linux, WebView2 on Windows, with a wire protocol designed for LLMs instead of for humans staring at DevTools. Login once, scrape JS-rendered pages, fill forms, take screenshots, drive your own app for smoke tests.

vibatchium

In its own words, on Official MCP Registry:

Stealth browser automation for AI agents — real Chrome, N parallel persistent logged-in sessions.

How to run each

vibesurfer As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vibesurfer@claude-community

vibatchium As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio vibatchium -- uvx vibatchium mcp

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

Neither one's marketplaces publish the settings it asks for.

What it can do: vibesurfer · What it can do: vibatchium · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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