Item detail
github.com

czlonkowski/n8n-mcp

czlonkowski/n8n-mcp is a developer tool that RepoRadar is tracking in its Radar section, currently rated Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 10.0 out of 10.

Score8.7
Popularity78.0
Riskconditional
TierGold
Score breakdown
Usefulness8.0
Novelty7.0
Momentum9.0
Maturity8.4
Open-source/build8.4
Evidence7.2
Workflow potential10.0
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for builders who want assistants to assemble or explain n8n automations with real node-level context instead of hallucinating from stale docs or generic workflow examples.

Where this stands now

czlonkowski/n8n-mcp ranks #43 of 2304 tracked Radar items by composite score (8.7 against a section median of 5.2). The section currently carries 1197 Bronze, 645 Gold, 462 Silver. RepoRadar has retained observations for this record since 2026-06-19 (100 days in the current window). Signal extremes versus the section: momentum at the 89th percentile.

Who should use it

automation builders n8n users MCP users developers building workflow assistants

Who should skip it

Move on from czlonkowski/n8n-mcp if the licensing terms, language support, or platform requirements do not fit your project.

About this signal

czlonkowski/n8n-mcp is tracked by RepoRadar as a developer tool in the Radar section. First seen 2026-06-19; the source record was last checked on 2026-06-19. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, czlonkowski/n8n-mcp is strongest on workflow potential (10.0) and momentum (9.0) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The czlonkowski/n8n-mcp record combines a 8.7/10 composite score with separate popularity (78.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.

Questions worth asking before you adopt this

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

The project is meant to improve AI-assisted workflow building around n8n, and its own README warns against editing production workflows directly with AI, so start on copies and test before promoting anything live.

Evidence links
Closest alternatives / related signals
n8n mcp workflow-automation developer-tools automation
Verification record

What RepoRadar actually verified

Installed and tested Source-only update since test

Hands-on setup or capability check retained by RepoRadar verification harness. Last checked 2026-07-13T03:21:43.688448Z.

A source release dated 2026-09-23 is newer than the retained test dated 2026-07-13; the previous test may no longer represent the current release.

Read as a sequence: 1 retained check(s) on 2026-07-13 with outcomes of 1 partial; evidence scopes covered bounded setup checks. Recorded setup time totals 0 minute(s).

partial · cohort-20260712-n8n-mcp-isolated

Tester
RepoRadar automated local verification harness
Started
2026-07-13T03:21:28.483395Z
Completed
2026-07-13T03:21:43.688448Z
Environment
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
0 minute(s)
Evidence scope
Bounded setup or capability check
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed. Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
  • Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
  • Executed bounded check: Resolve the n8n-mcp package and request its local command help.
  • Captured the complete sanitized stdout, stderr, exit status, and 15.21-second wall time.
Observed results
  • Command exited 0 after 15.21 seconds.
  • The command produced a successful local process exit; complete output is retained.
Observed strengths
  • The pinned [email protected] package launched its stdio process and handled closed stdin with explicit graceful-shutdown messages.
Friction
  • The command emitted stderr; warnings or errors are preserved in the retained log for review.
Limitations
  • No n8n credentials, MCP client, or live server workflow was used.
  • This bounded cohort check is not a production benchmark or a claim of real user-workflow adoption.

Pricing assessment: No paid plan or metered provider usage was exercised; package or licensing, hosting, and provider costs remain workflow-dependent.

Privacy assessment: No repository content, user data, or provider prompt was transmitted; broader product data handling was not assessed by this bounded run.

Open retained test log →

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

79 dated snapshots retained from 2026-06-19 through 2026-09-27; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.7 current · +0.0 net
Repository momentum9.3 current · +0.3 net
GitHub stars (observed)23,006 current · +737 net
GitHub stars23,006 exact observation
Versionv2.89.0
Last release2026-09-23T12:15:18Z
MaintenanceActive
Current riskConditional
Current verdictTry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineModel Context Protocol

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-09-278.79.323,006ConditionalTry nowActive
2026-09-268.79.323,000ConditionalTry nowActive
2026-09-258.79.322,995ConditionalTry nowActive
2026-09-248.79.322,989ConditionalTry nowActive
2026-09-238.79.322,982ConditionalTry nowActive
2026-09-228.79.022,972ConditionalTry nowActive
2026-09-218.79.022,967ConditionalTry nowActive
2026-09-208.79.322,952ConditionalTry nowActive
2026-09-198.79.022,945ConditionalTry nowActive
2026-09-178.79.022,911ConditionalTry nowActive
2026-09-158.79.322,885ConditionalTry nowActive
2026-09-138.79.022,878ConditionalTry nowActive

Why the record changed

Stars change

Stars changed: 23000 → 23006.

Stars change

Stars changed: 22995 → 23000.

Stars change

Stars changed: 22989 → 22995.

Stars change

Stars changed: 22983 → 22989.

Stars change

Stars changed: 22982 → 22983.

Stars change

Stars changed: 22972 → 22982.

Version change

Version changed: v2.87.0 → v2.89.0.

Stars change

Stars changed: 22969 → 22972.

Stars change

Stars changed: 22967 → 22969.

Stars change

Stars changed: 22962 → 22967.

Stars change

Stars changed: 22957 → 22962.

Stars change

Stars changed: 22952 → 22957.