Ext Ops Panel
Open dashboard
Comparison

Yarr MCP vs Jellyfin MCP Server

Yarr MCP is an MCP server published by dinglebear.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Jellyfin MCP Server is an MCP server published by AeLui. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
MarketplaceYarr MCPJellyfin MCP Server
Official MCP Registry Listed
Version: 2.2.2
Downloads/month (npm): 349
Downloads/week (npm): 75
Forks (GitHub): 5
Stars (GitHub): 17
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 2
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

Yarr MCP vs Jellyfin MCP Server
FactYarr MCPJellyfin MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)17 (better)2 (worse)
Forks (GitHub) (differs)5 (better)0 (worse)
Last release (differs)Not published2026-11-09
Where it runs (differs)On your machine (@dinglebear/yarr)Not stated
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)10, secrets among them: 3Not published
LicenceNot statedNot stated
Repository (differs)github.com/dinglebear-ai/yarrgithub.com/aelui/jellyfin-plugin-mcp
Changes in the last 7 days (differs)08
First seen (differs)2026-10-112026-11-03

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

Yarr MCP

In its own words, on Official MCP Registry:

Self-hosted media fleet operations across Sonarr, Radarr, Plex, and related apps over MCP and CLI.

Jellyfin MCP Server

In its own words, on Official MCP Registry:

Jellyfin plugin: search, play and manage your media library from AI assistants, per-user tokens.

How to run each

Yarr MCP As a local MCP server: npm package

Claude Code
claude mcp add --env "YARR_PLEX_TOKEN=<YOUR_YARR_PLEX_TOKEN>" --env "YARR_RADARR_API_KEY=<YOUR_YARR_RADARR_API_KEY>" --env "YARR_SONARR_API_KEY=<YOUR_YARR_SONARR_API_KEY>" --transport stdio yarr -- npx -y @dinglebear/yarr mcp

Requires: YARR_PLEX_TOKEN (secret), YARR_RADARR_API_KEY (secret), YARR_SONARR_API_KEY (secret)

Jellyfin MCP Server

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

The marketplaces of Jellyfin MCP Server publish no settings it asks for, so we do not compare settings.

What it can do: Yarr MCP · What it can do: Jellyfin MCP Server · Compare two other plugins

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