
N8n Manager MCP
Manage n8n workflows from your coding agent—list, create, sync, and update automations without leaving Claude Code or Cursor.
Overview
n8n Manager MCP is a Build-phase MCP server that lets AI coding agents view, create, sync, and manage n8n workflows over stdio.
What is this MCP server?
- MCP interface to n8n for viewing, creating, syncing, and managing workflows via natural language
- stdio transport via npx (`n8n-manager-mcp`, v0.1.0) for agent-first operators
- Reduces context switching between IDE chat and the n8n canvas when iterating webhooks and cron jobs
- Supports indie stacks that pair self-hosted or cloud n8n with Claude Code for ops automation
- Early v0.1.0 release—verify tool coverage against your n8n version and API credentials
- MCP server package version 0.1.0 (`n8n-manager-mcp`); stdio via npx
- Purpose-built for n8n workflow view, create, sync, and manage operations via AI
Community signal: 1 GitHub stars.
What problem does it solve?
Builders waste time alt-tabbing between n8n and their agent to tweak automations instead of driving workflow changes from the same MCP session.
Who is it for?
Solo founders who already use n8n for integrations and want agent-assisted workflow CRUD and sync during build and ops.
Skip if: Teams with no n8n instance, or those who need a full visual-only editor replacement without API-backed review gates.
What do I get? / Deliverables
After setup, your agent can query and mutate n8n workflows through MCP tools while you stay in Claude Code or Cursor.
- Created or updated n8n workflow definitions synced from agent sessions
- Inventory views of existing flows callable from the coding agent
- Repeatable MCP-based ops path for automation changes
Recommended MCP Servers
Journey fit
Build integrations is where solo builders connect agents to n8n; Grow lifecycle and Operate iterate reuse the same MCP bridge when tuning production workflows. integrations fits an MCP server that speaks to an external automation platform rather than in-repo application code.
How it compares
n8n workflow management MCP bridge—not a hosted n8n substitute or a generic HTTP REST skill.
Common Questions / FAQ
Who is N8n Manager MCP for?
It is for indie builders and operators who run n8n and want Claude Code, Cursor, or Codex to list, create, and sync workflows through MCP.
When should I use N8n Manager MCP?
Use it while building integrations or iterating post-launch when you need agent-driven changes to n8n flows, credentials permitting, with review on production workflows.
How do I add N8n Manager MCP to my agent?
Install `n8n-manager-mcp` via npx as a stdio MCP server in your client config, provide n8n base URL and API credentials per the GitHub repo, then restart the host.