Ext Ops Panel
Open dashboard
Comparison

context7 vs brewdoc

context7 is a plugin bundle for AI coding tools published by Upstash. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). brewdoc is a plugin bundle for AI coding tools published by Maksim Kochetkov. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-28. 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
Marketplacecontext7brewdoc
Claude Code: claude-plugins-official Listed
Version: not stated
Forks (GitHub): 4 698
Stars (GitHub): 45 000
Not marked · First seen
Not listed
Community marketplace kochetkov-ma/claude-brewcode Not listed Listed
Version: 6.12.5
Forks (GitHub): 4
Stars (GitHub): 39
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 brewdoc
Factcontext7brewdoc
Marketplaces that list it11
Stars (GitHub) (differs)45 000 (better)39 (worse)
Forks (GitHub) (differs)4 698 (better)4 (worse)
Last release (differs)Not published2026-10-26
Where it runs (differs)Remote server (mcp.context7.com/mcp)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)15
Licence (differs)Not statedMIT
Repository (differs)github.com/anthropics/claude-plugins-officialgithub.com/kochetkov-ma/claude-brewcode
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-25
Endpoint at the last check (differs)Responded 22 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.

brewdoc

In its own words, on Community GitHub marketplaces:

Brewdoc - Claude Code documentation tools: doc-staleness tracking, memory-sync generator, my-claude installation docs, Markdown to PDF, publishing to brewpage.app

How to run each

context7 As a Claude Code plugin

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

brewdoc As a Claude Code plugin

Claude Code
/plugin marketplace add kochetkov-ma/claude-brewcode
/plugin install brewdoc@claude-brewcode

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: brewdoc · 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 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.

Where the data comes from: how the catalog is built