Ext Ops Panel
Open dashboard
Comparison

claude-wave-plugin vs Context7

claude-wave-plugin is a plugin bundle for AI coding tools published by Harshvardhan Singh Chouhan. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Context7 is an MCP server published by upstash. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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
Marketplaceclaude-wave-pluginContext7
Community marketplace harshvardhan86/claude-wave-plugin Listed
Version: 0.2.1
Forks (GitHub): 3
Stars (GitHub): 13
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 4.4.4
Downloads/month (npm): 2 685 137
Downloads/week (npm): 561 384
Forks (GitHub): 3 123
Stars (GitHub): 63 415
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

claude-wave-plugin vs Context7
Factclaude-wave-pluginContext7
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)13 (worse)63 415 (better)
Forks (GitHub) (differs)3 (worse)3 123 (better)
Last release (differs)Not published2026-10-19
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Hooks it runs (differs)13Not published
Parts of the bundle (differs)151
LicenceMITMIT
Repository (differs)github.com/harshvardhan86/claude-wave-plugingithub.com/upstash/context7
Changes in the last 7 days (differs)210
First seen (differs)2026-10-202026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 37 h ago

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

claude-wave-plugin

In its own words, on Community GitHub marketplaces:

Wave-based engineering execution for Claude Code. Vendors the full v2 framework with hook enforcement of phase order, hand-off artifacts, model routing and orchestrator boundaries, plus full, demo and solo modes, token accounting and local checkpoints.

Context7

In its own words, on Official MCP Registry:

Up-to-date docs for AI agents

How to run each

claude-wave-plugin As a Claude Code plugin

Claude Code
/plugin marketplace add harshvardhan86/claude-wave-plugin
/plugin install claude-wave-plugin@claude-wave-plugin

Context7 As a remote MCP server

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

Requires: CONTEXT7_API_KEY (secret), Authorization header

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

The marketplaces of claude-wave-plugin publish no settings it asks for, so we do not compare settings.

What it can do: claude-wave-plugin · What it can do: Context7 · 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.

Where the data comes from: how the catalog is built