Vibeflow vs Granoflow
Vibeflow is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.
Vibeflow is a plugin bundle for AI coding tools published by Felipe Domingues. No marketplace we read lists it any more. Granoflow is an MCP server published by granoflow.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Granoflow | |
|---|---|---|
| Community marketplace domfelipe/vibeflow-n8n | Removed on 2026-10-26 Version: 0.9.0 Forks (GitHub): 0 Stars (GitHub): 10 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.16 Downloads/month (npm): 534 Downloads/week (npm): 37 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
| Fact | Vibeflowno longer listed · | Granoflow |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 10 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@granoflow/mcp-server) |
| Transport (differs) | Not stated | stdio |
| 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/domfelipe/vibeflow-n8n | github.com/granoflow/granoflow-mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Vibeflow
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Bridges n8n's workflow automation platform with AI models, providing access to 543 n8n nodes, workflow templates, and AI-capable automation tools.
-
Use this agent when you need to design, build, or validate n8n automation workflows. This agent specializes in creating efficient n8n workflows using proper validation techniques…
-
Migra workflows de n8n/Make al ecosistema Claude Code. Analiza JSONs, mapea nodos, propone arquitectura e implementa. Usa cuando el usuario pegue un JSON de n8n, mencione migrar…
-
Expert n8n workflow engineering skills for Claude Code. Uses n8n-manager, the n8nac CLI, and the n8n-as-code knowledge base to manage instances, search nodes, inspect schemas, and…
-
No-code workflow visualizer and automation blueprint builder.
-
Workflow-builder skill: design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) for Claude Code's Workflow tool (CLAUDE_CODE_WORKFLOWS=1…
What each says it does
Vibeflow
Audit and repair AI-generated n8n workflows before production
Granoflow
Connect MCP-capable AI agents to local Granoflow tasks, reviews, cards, imports, and work memory.
How to run each
Vibeflow
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Granoflow As a local MCP server: npm package
claude mcp add --transport stdio granoflow -- npx -y @granoflow/mcp-serverCommands 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: Vibeflow · What it can do: Granoflow · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.