Ext Ops Panel
Open dashboard
Comparison

todo4 vs io.github.rog0x/task

todo4 is a plugin bundle for AI coding tools published by panitw. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.rog0x/task is an MCP server published by rog0x. 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
Marketplacetodo4io.github.rog0x/task
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Downloads/month (npm): 154
Downloads/week (npm): 32
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

todo4 vs io.github.rog0x/task
Facttodo4io.github.rog0x/task
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (todo4.io/mcp)On your machine (@rog0x/mcp-task-tools)
Transport (differs)Streamable HTTPstdio
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/panitw/todo4-claude-plugingithub.com/rog0x/mcp-task-tools
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Answered with HTTP 404 (15 h ago)no remote endpoint we check

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

todo4

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

Todo4 gives Claude Code a durable memory for your work. Ask Claude to create tasks, log follow-ups mid-debugging, or break an epic into subtasks — and those tasks persist across sessions, projects, and even other agents (Claude Cowork, OpenClaw). There are 16 MCP tools cover the full lifecycle (create, update, close, comment, subtasks, tags, notifications) plus a /todo4:status command for a quick overdue / due-today dashboard. Free tier available, OAuth sign-in handles auth on first use.

io.github.rog0x/task

In its own words, on Official MCP Registry:

Todo, priority, estimation, burndown for AI agents

How to run each

todo4 As a Claude Code plugin

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

io.github.rog0x/task As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio task -- npx -y @rog0x/mcp-task-tools

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

Only todo4 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: todo4 · What it can do: io.github.rog0x/task · 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