Ext Ops Panel
Open dashboard
Comparison

n8n vs AI Workbench MCP

n8n is an MCP server published by czlonkowski. Marketplaces we read that list it: 1 (Docker MCP Catalog). AI Workbench MCP is an MCP server published by alptugharun. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplacen8nAI Workbench MCP
Docker MCP Catalog Listed
Version: sha256:061cdb8fbaa7
Forks (GitHub): 3 673
Pulls (Docker Hub): 157 864
Stars (Docker Hub): 23
Stars (GitHub): 23 144
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0a2
Downloads/month (PyPI): 149
Downloads/week (PyPI): 35
Forks (GitHub): 0
Stars (GitHub): 1
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 AI Workbench MCP
Factn8nAI Workbench MCP
Marketplaces that list it11
Stars (GitHub) (differs)23 144 (better)1 (worse)
Pulls (Docker Hub) (differs)157 864No figure on Docker Hub
Forks (GitHub) (differs)3 673 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/n8n)On your machine (alptugharun-ai-workbench-mcp)
Transportstdiostdio
Tools it declares (differs)42Not published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/czlonkowski/n8n-mcpgithub.com/alptugharun/ai-workbench-mcp
Changes in the last 7 days00
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

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.

AI Workbench MCP

In its own words, on Official MCP Registry:

Read-only MCP server for reusable AI prompts and assistant blueprints.

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)

AI Workbench MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio ai-workbench-mcp -- uvx alptugharun-ai-workbench-mcp

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

Tools each declares

The marketplaces of AI Workbench MCP publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: n8n · What it can do: AI Workbench MCP · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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