Ext Ops Panel
Open dashboard
Comparison

context7 vs com.vibgrate/ai-context

context7 is a plugin bundle for AI coding tools published by Upstash. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). com.vibgrate/ai-context is an MCP server published by vibgrate.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
Marketplacecontext7com.vibgrate/ai-context
Claude Code: claude-plugins-official Listed
Version: not stated
Forks (GitHub): 4 598
Stars (GitHub): 43 563
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2026.1020.1
Downloads/month (npm): 4 835
Downloads/week (npm): 581
Forks (GitHub): 9
Stars (GitHub): 5
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

context7 vs com.vibgrate/ai-context
Factcontext7com.vibgrate/ai-context
Marketplaces that list it11
Stars (GitHub) (differs)43 563 (better)5 (worse)
Forks (GitHub) (differs)4 598 (better)9 (worse)
Last release (differs)Not published2026-10-21
Where it runs (differs)Remote server (mcp.context7.com/mcp)On your machine (@vibgrate/cli)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/claude-plugins-officialgithub.com/vibgrate/cli
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 42 h agono remote endpoint we check

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

context7

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

Upstash Context7 MCP server for up-to-date documentation lookup. Connects to Context7's hosted remote MCP server (https://mcp.context7.com/mcp) — no local Node.js or npx required — to pull version-specific documentation and code examples directly from source repositories into your LLM context. Works anonymously out of the box; set CONTEXT7_API_KEY for higher rate limits.

com.vibgrate/ai-context

In its own words, on Official MCP Registry:

Local-first MCP server: version-correct library docs, code map, and offline drift for your repo.

How to run each

context7 As a Claude Code plugin

Claude Code
/plugin install context7@claude-plugins-official

com.vibgrate/ai-context As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio ai-context -- npx -y -p @vibgrate/cli vg serve

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

Only context7 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: context7 · What it can do: com.vibgrate/ai-context · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/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