Ext Ops Panel
Open dashboard
Comparison

n8n vs io.github.theluckystrike/budget-tracker

n8n is an MCP server published by czlonkowski. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.theluckystrike/budget-tracker is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacen8nio.github.theluckystrike/budget-tracker
Docker MCP Catalog Listed
Version: sha256:061cdb8fbaa7
Forks (GitHub): 3 664
Pulls (Docker Hub): 154 532
Stars (Docker Hub): 23
Stars (GitHub): 23 089
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.22.0
Forks (GitHub): 0
Stars (GitHub): 2
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 io.github.theluckystrike/budget-tracker
Factn8nio.github.theluckystrike/budget-tracker
Marketplaces that list it11
Stars (GitHub) (differs)23 089 (better)2 (worse)
Pulls (Docker Hub) (differs)154 532No figure on Docker Hub
Forks (GitHub) (differs)3 664 (better)0 (worse)
Last release (differs)Not published2026-10-14
Where it runs (differs)On your machine (mcp/n8n)Remote server or your machine
Transport (differs)stdioStreamable HTTP, stdio
Tools it declares (differs)42Not published
Environment variables it asks for (differs)3, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/czlonkowski/n8n-mcpgithub.com/theluckystrike/mcp-servers
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 28 h ago

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.

io.github.theluckystrike/budget-tracker

In its own words, on Official MCP Registry:

Track budgets from your AI chat: envelopes, monthly limits, variance reports. All data is local.

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)

io.github.theluckystrike/budget-tracker As a remote MCP server

Claude Code
claude mcp add --transport http budget-tracker https://mcp.zovo.one/mcp/budget-tracker --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: MCP_LICENSE_KEY (secret), Authorization header

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

Only io.github.theluckystrike/budget-tracker has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of io.github.theluckystrike/budget-tracker publish no list of tools, so we do not compare tools.

Settings each asks for

Only n8n asks for

  • MCP_MODE
  • N8N_API_KEY (secret)
  • N8N_API_URL

Only io.github.theluckystrike/budget-tracker asks for

  • MCP_LICENSE_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: n8n · What it can do: io.github.theluckystrike/budget-tracker · 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