Ext Ops Panel
Open dashboard
Comparison

Task Queuer vs io.github.codellyson/passalong

Task Queuer is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.codellyson/passalong is an MCP server published by codellyson. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-22. 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
MarketplaceTask Queuerio.github.codellyson/passalong
Community marketplace danielrosehill/claude-code-plugins Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.13.1
Downloads/month (npm): 3 067
Downloads/week (npm): 621
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.21.0
Downloads/month (npm): 3 067
Downloads/week (npm): 621
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

Task Queuer vs io.github.codellyson/passalong
FactTask Queuerio.github.codellyson/passalong
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-17
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 forNot publishedNot published
Parts of the bundle (differs)6Not a bundle
LicenceMITMIT
Repository (differs)github.com/danielrosehill/claude-task-queuer-plugingithub.com/codellyson/passalong
Changes in the last 7 days22
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago, requires a key

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

Task Queuer

In its own words, on Community GitHub marketplaces:

Repo-based task queueing system with categorisation and prioritisation. Scaffolds a planning/ folder, logs tasks (single, batch list, or voice-transcribed), buckets them by category, and hands prioritised work off to the repo's orchestration agent.

io.github.codellyson/passalong

In its own words, on Official MCP Registry:

Hand tasks, bugs and finished work to AI coding agents, and get back a write-up with evidence.

How to run each

Task Queuer As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install task-queuer@danielrosehill

io.github.codellyson/passalong As a remote MCP server

Claude Code
claude mcp add --transport http passalong https://passalong.dev/v1/mcp

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

Only io.github.codellyson/passalong 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: Task Queuer · What it can do: io.github.codellyson/passalong · 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