Ext Ops Panel
Open dashboard
Comparison

Noeto vs Vibeflow

Noeto is an MCP server published by noeto-tasks. Marketplaces we read that list it: 1 (Official MCP Registry). Vibeflow is an MCP server published by zorcec. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
MarketplaceNoetoVibeflow
Official MCP Registry Listed
Version: 0.6.5
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.26.0
Downloads/month (npm): 2 680
Downloads/week (npm): 604
Forks (GitHub): 0
Stars (GitHub): 2
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

Noeto vs Vibeflow
FactNoetoVibeflow
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last release (differs)Not published2026-11-04
Where it runs (differs)On your machine (ghcr.io/noeto-tasks/noeto-mcp:v0.6.5)On your machine (@vibeflow-tools/cli)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/noeto-tasks/noeto-mcpgithub.com/zorcec/vibeflow
Changes in the last 7 days (differs)04
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

Noeto

In its own words, on Official MCP Registry:

Work a Noeto kanban board: read and search it, create, move and comment on cards, keep docs on them.

Vibeflow

In its own words, on Official MCP Registry:

Task management for AI coding agents over MCP — board, CLI tools, plus UI annotation.

How to run each

Noeto As a local MCP server: Docker image

Claude Code
claude mcp add --env "NOETO_API_URL=<YOUR_NOETO_API_URL>" --env "NOETO_TOKEN=<YOUR_NOETO_TOKEN>" --transport stdio noeto-mcp -- docker run -i --rm -e NOETO_API_URL -e NOETO_TOKEN ghcr.io/noeto-tasks/noeto-mcp:v0.6.5

Requires: NOETO_API_URL, NOETO_TOKEN (secret)

Vibeflow As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio vibeflow -- npx -y @vibeflow-tools/cli

Requires: --project

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

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

What it can do: Noeto · What it can do: Vibeflow · Compare two other plugins

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