Ext Ops Panel
Open dashboard
Comparison

vibecircle vs GitHub

vibecircle is a plugin bundle for AI coding tools published by miltonian. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). GitHub is an MCP server published by github. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-13. 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
MarketplacevibecircleGitHub
Claude Code: claude-plugins-community Listed
Version: bf8b30f
Forks (GitHub): 2
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.0.2
Forks (GitHub): 5 134
Stars (GitHub): 33 552
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:ffced0d76e77
Forks (GitHub): 5 134
Stars (GitHub): 33 552
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

vibecircle vs GitHub
FactvibecircleGitHub
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)4 (worse)33 552 (better)
Forks (GitHub) (differs)2 (worse)5 134 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP, stdio
Tools it declares (differs)Not published40
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/miltonian/vibecirclegithub.com/github/github-mcp-server
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

vibecircle

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

See what your friends are building. A social feed for friend groups who vibe code — share screenshots, deploy links, and coding activity with your circle. Features: auto-capture from Claude Code via /share command, live app embeds, reactions and comments, ambient presence (see who's building right now), and AI-powered project explanations (BYOK). Includes /circle setup for zero-friction device code authentication, and /share for posting updates. Open source, MIT licensed.

GitHub

In its own words, on Official MCP Registry:

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

How to run each

vibecircle As a Claude Code plugin

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

GitHub As a remote MCP server

Claude Code
claude mcp add --transport http github-mcp-server https://api.githubcopilot.com/mcp/ --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Tools each declares

The marketplaces of vibecircle publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of vibecircle publish no settings it asks for, so we do not compare settings.

What it can do: vibecircle · What it can do: GitHub · 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 the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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