Summary
n8n-mcp is gaining traction as an MCP server that gives coding agents structured access to n8n nodes, templates, and workflow operations. The project now spans both hosted and self-hosted usage, positioning itself as reusable workflow plumbing for Claude Code, Cursor, Windsurf, Codex, and related agent clients.
What changed
n8n-mcp continued to break out as an MCP bridge that lets coding agents build and work with n8n workflows through a shared integration layer.
Why it matters
Workflow automation is becoming a core extension point for coding agents, but teams do not want to rebuild that connector separately for every client. n8n-mcp matters because it turns n8n workflow access into a reusable substrate that multiple agent runtimes can share, making automation more portable and less vendor-specific.
Evidence excerpt
The project describes itself as an MCP server for Claude Desktop, Claude Code, Windsurf, Cursor, and Codex, and says it provides structured access to n8n nodes, templates, and workflow operations across hosted and self-hosted setups.