Ext Ops Panel
Open dashboard
Comparison

learn vs org.llmref/llmref

learn is a plugin bundle for AI coding tools published by agent-sh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). org.llmref/llmref is an MCP server published by llmref.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplacelearnorg.llmref/llmref
Claude Code: claude-plugins-community Listed
Version: 5.1.0
Forks (GitHub): 1
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
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

learn vs org.llmref/llmref
Factlearnorg.llmref/llmref
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.llmref.org/v1/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/agent-sh/learngithub.com/reclear-io/llmref-plugin
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

learn

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

Research any topic online and create comprehensive learning guides with RAG-optimized indexes for your AI agents. `/learn react hooks` searches the web for ~20 sources, scores each on a 100-point scale across authority (3x), recency (2x), depth (2x), examples (2x), and uniqueness (1x), fetches only high-scoring sources, and writes a synthesized guide to `agent-knowledge/<topic>.md` with companion `resources/<topic>-sources.json` containing full source metadata. Six-stage methodology: progressive discovery, quality scoring, just-in-time extraction, synthesis, source citation, RAG optimization. Output shape designed for ingestion by Claude Code, OpenCode, and Codex agent-knowledge libraries.

org.llmref/llmref

In its own words, on Official MCP Registry:

Versioned documentation registry and semantic search for AI tools and coding assistants.

How to run each

learn As a Claude Code plugin

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

org.llmref/llmref As a remote MCP server

Claude Code
claude mcp add --transport http llmref https://api.llmref.org/v1/mcp

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

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: learn · What it can do: org.llmref/llmref · 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