Awesome Autoloop vs com.vibsync/vibsync
Awesome Autoloop is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
Awesome Autoloop is a plugin bundle for AI coding tools published by suhang56. No marketplace we read lists it any more. com.vibsync/vibsync is an MCP server published by vibsync.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  com.vibsync/vibsync | |
|---|---|---|
| Community marketplace bangdream-na/awesome-autoloop | Removed on 2026-10-15 Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | Awesome Autoloopno longer listed · | com.vibsync/vibsync |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| 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 |
| Hooks it runs (differs) | 117 | Not published |
| Parts of the bundle (differs) | 21 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/bangdream-na/awesome-autoloop | github.com/loosedays/vibsync-mcp |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Awesome Autoloop
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Endor Labs workflow agents and setup for Claude Code.
-
Endor Labs workflow agents and setup for Claude Code.
-
10 slash commands and 3 agent definitions distilled from 6 months of daily Claude Code use. Not a framework -- just the patterns that survived: multi-agent build pipelines…
-
Evidence-first Claude Code plugin for repeatable, spec-driven development workflows.
-
cc-bootstrapper
Automation bootstrap for Claude Code. Analyzes any project and generates a complete .claude/ structure with agents, pipelines, skills, memory, hooks, and settings.
-
Multi-agent development harness for Claude Code. Your AI has speed; we give it direction — through living specs and focused specialist agents.
What each says it does
Awesome Autoloop
An opinionated 6-agent pipeline + enforcement-hook framework for Claude Code.
com.vibsync/vibsync
One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.
How to run each
Awesome Autoloop
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
com.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: Awesome Autoloop · What it can do: com.vibsync/vibsync · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.