io.github.HomenShum/nodebench vs io.github.leonardosepulvedat/mcp-n8n
io.github.HomenShum/nodebench is an MCP server published by HomenShum. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). io.github.leonardosepulvedat/mcp-n8n is an MCP server published by leonardosepulvedat. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 2.31.2 Downloads/month (npm): 433 Downloads/week (npm): 52 Forks (GitHub): 3 Stars (GitHub): 15 Not marked · First seen |
Listed Version: 1.5.0 Downloads/month (npm): 794 Downloads/week (npm): 169 Forks (GitHub): 3 Stars (GitHub): 21 Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 9d6bf19 Forks (GitHub): 3 Stars (GitHub): 15 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 1.5.0 Downloads/month (npm): 794 Downloads/week (npm): 169 Forks (GitHub): 3 Stars (GitHub): 21 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 | io.github.HomenShum/nodebench | io.github.leonardosepulvedat/mcp-n8n |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 15 (worse) | 21 (better) |
| Forks (GitHub) | 3 | 3 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (nodebench-mcp) | On your machine (mcp-n8n) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/homenshum/nodebench-ai | github.com/leonardosepulvedat/mcp-n8n |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
io.github.HomenShum/nodebench
260 MCP tools across 49 domains. AI Flywheel, quality gates, research, web scraping.
io.github.leonardosepulvedat/mcp-n8n
Operate and build n8n: 61 tools, 560-node catalog, validation, autofix, snapshots and backups.
How to run each
io.github.HomenShum/nodebench As a local MCP server: npm package
claude mcp add --transport stdio nodebench -- npx -y nodebench-mcp
io.github.leonardosepulvedat/mcp-n8n As a local MCP server: npm package
claude mcp add --env "N8N_API_KEY=<YOUR_N8N_API_KEY>" --env "N8N_BASE_URL=<YOUR_N8N_BASE_URL>" --transport stdio mcp-n8n -- npx -y mcp-n8n
Requires: N8N_API_KEY (secret), N8N_BASE_URL
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 io.github.HomenShum/nodebench publish no settings it asks for, so we do not compare settings.
What it can do: io.github.HomenShum/nodebench · What it can do: io.github.leonardosepulvedat/mcp-n8n · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.