vibecircle vs com.vibsync/vibsync
vibecircle is a plugin bundle for AI coding tools published by miltonian. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). com.vibsync/vibsync is an MCP server published by vibsync.com. 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
| Marketplace |  vibecircle |  com.vibsync/vibsync |
|---|---|---|
| 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: 0.2.3 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
| Fact | vibecircle | com.vibsync/vibsync |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 4 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 2 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.vibsync.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not published | 2 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/miltonian/vibecircle | github.com/loosedays/vibsync-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 46 h ago, requires a key |
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
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.
com.vibsync/vibsync
One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.
How to run each
vibecircle As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vibecircle@claude-communitycom.vibsync/vibsync As a remote MCP server
claude mcp add --transport http vibsync https://mcp.vibsync.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.vibsync/vibsync has a remote endpoint we check. How we check endpoints
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: vibecircle · What it can do: com.vibsync/vibsync · 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.