Ext Ops Panel
Open dashboard
Comparison

chub vs ai.byteask/embedded-docs

chub is a plugin bundle for AI coding tools published by naga-k. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ai.byteask/embedded-docs is an MCP server published by byteask.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplacechubai.byteask/embedded-docs
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Forks (GitHub): 4
Stars (GitHub): 25
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

chub vs ai.byteask/embedded-docs
Factchubai.byteask/embedded-docs
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)25 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.byteask.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/naga-k/chub-claude-plugingithub.com/byteask/byteask-embedded-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 1 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

chub

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

Fetches curated, versioned API docs from Context Hub before writing code — so Claude uses current APIs instead of hallucinating from training data. Auto-installs via npx (no global setup), refreshes the doc registry each session, and supports search, annotations, and feedback. Works with 1500+ documented libraries including OpenAI, Stripe, Anthropic, and more.

ai.byteask/embedded-docs

In its own words, on Official MCP Registry:

Page-cited retrieval for embedded docs, datasheets, MISRA, CMSIS, and RTOS references.

How to run each

chub As a Claude Code plugin

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

ai.byteask/embedded-docs As a remote MCP server

Claude Code
claude mcp add --transport http embedded-docs https://mcp.byteask.ai/mcp

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

Only ai.byteask/embedded-docs 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: chub · What it can do: ai.byteask/embedded-docs · 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