Ext Ops Panel
Open dashboard
Comparison

learning-planner vs MCP Task Orchestrator

learning-planner is a plugin bundle for AI coding tools published by SPYfighting. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). MCP Task Orchestrator is an MCP server published by jpicklyk. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-14. 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
Marketplacelearning-plannerMCP Task Orchestrator
Claude Code: claude-plugins-community Listed
Version: ecb9a67
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.16.0
Forks (GitHub): 24
Stars (GitHub): 207
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:eab0bb62611a
Forks (GitHub): 24
Stars (GitHub): 207
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

learning-planner vs MCP Task Orchestrator
Factlearning-plannerMCP Task Orchestrator
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)207 (better)
Forks (GitHub) (differs)0 (worse)24 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (ghcr.io/jpicklyk/task-orchestrator:3.16.0)
Transport (differs)Not statedstdio
Tools it declares (differs)Not published42
Environment variables it asks for (differs)Not published7, secrets among them: 0
Parts of the bundle (differs)1Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/spyfighting/learning-plannergithub.com/jpicklyk/task-orchestrator
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

learning-planner

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

A Claude Code plugin that acts as your long-running learning companion — helps you plan, track, and review self-directed learning in structured phases.

MCP Task Orchestrator

In its own words, on Official MCP Registry:

Server-enforced workflow discipline for AI agents: work items, dependency graphs, quality gates

How to run each

learning-planner As a Claude Code plugin

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

MCP Task Orchestrator As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio task-orchestrator -- docker run -i --rm -v mcp-task-data:/app/data ghcr.io/jpicklyk/task-orchestrator:3.16.0

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

Tools each declares

The marketplaces of learning-planner publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of learning-planner publish no settings it asks for, so we do not compare settings.

What it can do: learning-planner · What it can do: MCP Task Orchestrator · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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