n8n-mcp

MCP server enabling n8n workflow automation to use Model Context Protocol tools.

A single Bluesky mention (#2 in a tiny 4-row pool) is the only signal for this n8n-MCP bridge. No GitHub, HN, X, Reddit, or developer blog traction exists. The MCP ecosystem is growing, but this specific repository lacks cross-source validation.

Why now: MCP protocol hype is peaking; low-effort bridges get brief social mentions without adoption.

• Only Bluesky signal (rank 2 of 4 rows) with zero engagement metrics
• GitHub absent from sourceStats despite 100 tracked repos — not in top 100
• No HN, X, Reddit, Product Hunt, or Dev.to presence
• 178 of 200 pool entries are single_source — this fits the noise pattern

Considerations: MCP+n8n is a plausible integration, but a single social mention without GitHub stars, issues, or forks suggests either very early pre-launch or manufactured buzz. Bluesky's tiny 4-row sample size means rank 2 is statistically meaningless.

EMERGING SIGNAL · Ignore: Revisit only if GitHub stars >100 or HN/Reddit organic discussion emerges.

Sources: Bluesky search: czlonkowski/n8n-mcp