Summary

The n8n-mcp repository continues to gain attention as an MCP server that lets Claude Desktop, Claude Code, Windsurf, and Cursor build n8n workflows directly. Its current GitHub footprint is large enough to matter as ecosystem plumbing rather than a niche side project.

What changed

n8n-mcp kept gaining public momentum as a cross-client MCP bridge for building and editing n8n workflows from coding agents.

Why it matters

Workflow automation is becoming a core extension point for coding agents. If n8n-style orchestration becomes easy to drive from Claude Code, Cursor, and Windsurf through one MCP layer, automation moves closer to a shared execution substrate instead of vendor-specific glue.

Evidence excerpt

The repo presents n8n-mcp as an MCP for Claude Desktop, Claude Code, Windsurf, and Cursor to build n8n workflows, and the project now shows substantial public adoption on GitHub.

Sources