Ext Ops Panel
Open dashboard
Comparison

n8n vs ibl.ai vibe

n8n is an MCP server published by czlonkowski. Marketplaces we read that list it: 1 (Docker MCP Catalog). ibl.ai vibe is a plugin bundle for AI coding tools published by ibl.ai. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-27. 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
Marketplacen8nibl.ai vibe
Docker MCP Catalog Listed
Version: sha256:061cdb8fbaa7
Forks (GitHub): 3 673
Pulls (Docker Hub): 158 228
Stars (Docker Hub): 23
Stars (GitHub): 23 144
Not marked · First seen
Not listed
Community marketplace iblai/vibe Not listed Listed
Version: not stated
Forks (GitHub): 7
Stars (GitHub): 15
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

n8n vs ibl.ai vibe
Factn8nibl.ai vibe
Marketplaces that list it11
Stars (GitHub) (differs)23 144 (better)15 (worse)
Pulls (Docker Hub) (differs)158 228No figure on Docker Hub
Forks (GitHub) (differs)3 673 (better)7 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/n8n)On your machine (@iblai/mcp)
Transport (differs)stdioNot stated
Tools it declares (differs)42Not published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle161
LicenceMITMIT
Repository (differs)github.com/czlonkowski/n8n-mcpgithub.com/iblai/vibe
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-21

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

n8n

In its own words, on Docker MCP Catalog:

Bridges n8n's workflow automation platform with AI models, providing access to 543 n8n nodes, workflow templates, and AI-capable automation tools.

ibl.ai vibe

In its own words, on Community GitHub marketplaces:

Build apps on ibl.ai and operate the platform headlessly — 136 skills (iblai-vibe-* with visual components, iblai-api-* headless), the /iblai-vibe-start intake, and the @iblai/mcp SDK-docs server.

How to run each

n8n As a local MCP server: Docker image

Claude Code
claude mcp add --env "N8N_API_KEY=<YOUR_N8N_API_KEY>" --transport stdio n8n -- docker run -i --rm -e N8N_API_KEY mcp/n8n

Requires: N8N_API_KEY (secret)

ibl.ai vibe As a Claude Code plugin

Claude Code
/plugin marketplace add iblai/vibe
/plugin install iblai-vibe@iblai

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

Tools each declares

The marketplaces of ibl.ai vibe publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: n8n · What it can do: ibl.ai vibe · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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