flow vs LooperTask
flow is a plugin bundle for AI coding tools published by prajyotbankade. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). LooperTask is an MCP server published by loopertask.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
| Marketplace |  flow | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.1.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 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
| Fact | flow | LooperTask |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (loopertask.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/prajyotbankade/flow | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not 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
flow
Flow turns Claude into a project partner who manages your backlog. Say "park this for later," and it queues the idea. Say "what's next?" and it finds the highest-priority ready item and offers to start, handling the bookkeeping so you stay in flow. It works as a lightweight scrum board with three ways to interact: talk to Claude conversationally, drag cards on the built-in Kanban board, or run multiple agents in parallel, each with filtered views. All three read and write the same backlog.json, no sync step, no drift. Lanes are fully configurable. Start with the default agile flow (Backlog → Refined → Ready → In Progress → Code Review → Done) or define your own columns and gate rules. The board, the API, and the agent all enforce them consistently. Conversational management: Add, reorder, refine, and complete items by talking naturally; no commands to memorize. Built-in Kanban board: Drag-and-drop web UI that syncs with the agent in real time; launch with one command. Multi-agent support: Leader agents assign
LooperTask
AI-native Kanban board — connect Claude to claim, work and move your tasks over MCP.
How to run each
flow As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install flow@claude-communityLooperTask As a remote MCP server
claude mcp add --transport http loopertask https://loopertask.com/mcpCommands 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: flow · What it can do: LooperTask · 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.