Ext Ops Panel
Open dashboard
Comparison

next-task vs cloud.tri2b/projects

next-task is a plugin bundle for AI coding tools published by agent-sh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). cloud.tri2b/projects is an MCP server published by tri2b.cloud. 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
Marketplacenext-taskcloud.tri2b/projects
Claude Code: claude-plugins-community Listed
Version: 5.1.0
Forks (GitHub): 2
Stars (GitHub): 7
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.8.5
No figure published
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

next-task vs cloud.tri2b/projects
Factnext-taskcloud.tri2b/projects
Marketplaces that list it11
Stars (GitHub) (differs)7No figure on GitHub
Forks (GitHub) (differs)2No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.projects.tri2b.cloud/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)12Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/agent-sh/next-taskNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

next-task

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

Autonomous workflow orchestrator that takes a task from discovery to production through 12 coordinated phases — exploration, planning, implementation, multi-agent review, and shipping. Pick a task from GitHub/GitLab/local sources, approve a plan, and the rest runs autonomously: git worktree creation, code generation, deslop, agnix, audit-project review loop, sync-docs, gate-and-ship. Two-file state management lets you `--resume` from any phase across session boundaries. 8 specialist agents with model selection (opus for exploration/planning, sonnet for review/CI, haiku for mechanical execution) keep token costs predictable. Workflow enforcement gates prevent skipping reviews or tests.

cloud.tri2b/projects

In its own words, on Official MCP Registry:

Task tracking built for coding agents. Work is leased, so two agents never take the same SubTask.

How to run each

next-task As a Claude Code plugin

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

cloud.tri2b/projects As a remote MCP server

Claude Code
claude mcp add --transport http projects https://mcp.projects.tri2b.cloud/mcp

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

Neither one's marketplaces publish the settings it asks for.

What it can do: next-task · What it can do: cloud.tri2b/projects · 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