Ext Ops Panel
Open dashboard
Comparison

n8n vs @lovable.dev/mcp-js

n8n is an MCP server published by czlonkowski. Marketplaces we read that list it: 3 (Docker MCP Catalog, npm registry (MCP servers), Community GitHub marketplaces). @lovable.dev/mcp-js is an MCP server published by @lovable.dev. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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
Marketplacen8n@lovable.dev/mcp-js
Docker MCP Catalog Listed
Version: sha256:061cdb8fbaa7
Forks (GitHub): 3 683
Pulls (Docker Hub): 163 446
Stars (Docker Hub): 24
Stars (GitHub): 23 228
Not marked · First seen
Not listed
npm registry (MCP servers) Listed
Version: 2.101.4
Downloads/month (npm): 298 715
Downloads/week (npm): 83 221
Forks (GitHub): 3 683
Stars (GitHub): 23 228
Not marked · First seen
Listed
Version: 3.4.0
Downloads/month (npm): 1 432 879
Downloads/week (npm): 546 524
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 @lovable.dev/mcp-js
Factn8n@lovable.dev/mcp-js
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)23 228No figure on GitHub
Pulls (Docker Hub) (differs)163 446No figure on Docker Hub
Forks (GitHub) (differs)3 683No figure on GitHub
Last release (differs)2026-11-08 (better)2026-10-30 (worse)
Where it runs (differs)On your machine (mcp/n8n)On your machine (@lovable.dev/mcp-js)
Transport (differs)stdioNot stated
Tools it declares (differs)42Not published
Environment variables it asks for (differs)5, secrets among them: 1Not published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)2Not a bundle
LicenceMITMIT
Repository (differs)github.com/czlonkowski/n8n-mcpgithub.com/lovablelabs/lovable
Changes in the last 7 days (differs)40
First seen (differs)2026-10-112026-10-12

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.

@lovable.dev/mcp-js

In its own words, on npm registry (MCP servers):

Author MCP servers for Lovable apps. Declare tools with defineTool, register them in defineMcp, and a framework adapter (TanStack or Supabase Edge Functions) emits the route(s) at build time.

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)

@lovable.dev/mcp-js

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Tools each declares

The marketplaces of @lovable.dev/mcp-js publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of @lovable.dev/mcp-js publish no settings it asks for, so we do not compare settings.

What it can do: n8n · What it can do: @lovable.dev/mcp-js · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). 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