Ext Ops Panel
Open dashboard
Comparison

youtube-agent vs posterly

youtube-agent is a plugin bundle for AI coding tools published by Jake Schincariol. Marketplaces we read that list it: 1 (Community GitHub marketplaces). posterly is an MCP server published by awpthorp. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-23. 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
Marketplaceyoutube-agentposterly
Community marketplace jakeschincariol/youtube-agent-skill Listed
Version: 1.0.0
Forks (GitHub): 803
Stars (GitHub): 2 493
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.53.3
Downloads/month (npm): 7 064
Downloads/week (npm): 936
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.55.1
Downloads/month (npm): 7 064
Downloads/week (npm): 936
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

youtube-agent vs posterly
Factyoutube-agentposterly
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 493 (better)0 (worse)
Forks (GitHub) (differs)803 (better)0 (worse)
Last release (differs)Not published2026-10-23
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 published2, secrets among them: 1
Parts of the bundle (differs)11Not a bundle
LicenceMITMIT
Repository (differs)github.com/jakeschincariol/youtube-agent-skillgithub.com/awpthorp/posterly-mcp-server
Changes in the last 7 days (differs)211
First seen (differs)2026-10-222026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 20 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

youtube-agent

In its own words, on Community GitHub marketplaces:

Eleven Claude skills that run a YouTube channel, including a scored hook panel, a title and thumbnail linter, an edit decision list, a retention reader and a virality engine.

posterly

In its own words, on Official MCP Registry:

Validate, schedule, publish, and analyze social content across 18 platforms with posterly.

How to run each

youtube-agent As a Claude Code plugin

Claude Code
/plugin marketplace add jakeschincariol/youtube-agent-skill
/plugin install youtube-agent@youtube-agent-skill

posterly As a remote MCP server

Claude Code
claude mcp add --transport http posterly https://www.poster.ly/api/mcp

Requires: POSTERLY_API_KEY (secret)

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

Only posterly 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 youtube-agent publish no settings it asks for, so we do not compare settings.

What it can do: youtube-agent · What it can do: posterly · 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. Package data comes from the public npm registry (registry.npmjs.org). 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