Score breakdown
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.
Who should use it
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. It was first seen on 2026-06-19 and last updated 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. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned czlonkowski/n8n-mcp a composite score of 8.7 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 78.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
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.