Ext Ops Panel
Open dashboard
Comparison

vibelearn vs Vibe Coding 中文助手

vibelearn is a plugin bundle for AI coding tools published by anergcorp. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Vibe Coding 中文助手 is an MCP server published by menghaoran214-lang. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
MarketplacevibelearnVibe Coding 中文助手
Claude Code: claude-plugins-community Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.6.0
No figure published
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

vibelearn vs Vibe Coding 中文助手
FactvibelearnVibe Coding 中文助手
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (n8n.xiaomeng.ink/mcp/vibe-coding-cn)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)AGPL-3.0Not stated
Repository (differs)github.com/anergcorp/vibelearnNot stated
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 responding since 2026-10-14

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

vibelearn

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

VibeLearn silently watches your Claude Code sessions, extracts the concepts you encounter while building, and turns them into personalized quiz questions — so you actually retain what you learn. After each session, run `vl quiz` to review with adaptive spaced repetition across 7 question formats (multiple choice, spot the bug, code reading, fill in the blank, open-ended, true/false, ordering). Difficulty adjusts automatically: 3 correct answers in a row promotes you to the next level, one wrong answer drops you back. Senior-level open-ended answers are evaluated by a 5-dimension AI rubric.

Vibe Coding 中文助手

In its own words, on Official MCP Registry:

Read-only Chinese Vibe Coding knowledge connector for search, docs, and repo freshness.

How to run each

vibelearn As a Claude Code plugin

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

Vibe Coding 中文助手 As a remote MCP server

Claude Code
claude mcp add --transport http vibe-coding-cn https://n8n.xiaomeng.ink/mcp/vibe-coding-cn

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

Only Vibe Coding 中文助手 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: vibelearn · What it can do: Vibe Coding 中文助手 · 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