MCP server
Ship n8n workflows from your editor.
One endpoint. Claude, Cursor, or any Streamable HTTP client. Search nodes, build workflows, and diagnose failures without leaving the window you are in.
- 01
Ask in plain language
"Watch a Stripe webhook, enrich in HubSpot, write a row to Postgres." Your client calls the tools.
- 02
Get a workflow, not a guess
Built from the node catalog on your instance and validated before you see it.
- 03
Approve before it ships
Anything that writes to your instance waits for you. Models get no shortcut.
MCP server
Or never leave your editor at all.
Same builder, same instance, same live test. Every approval gate still applies when the caller is a model.
- Claude
- Claude Code
- Cursor
- Windsurf
Read only
- search_nodes
- get_node
- get_workflow_patterns
- get_best_practices
- list_workflows
- get_workflow
- n8n_validate_workflow
Writes, labelled as such
- n8n_create_workflow
- n8n_update_workflow
- adopt_n8n_workflow
Touches production, flagged destructive
- n8n_execute_and_diagnose
- n8n_heal_workflow
- n8n_watch_workflow
- update_native_workflow
- restore_workflow_snapshot
Questions
MCP questions, answered.
If your client speaks Streamable HTTP MCP, it works. Here is what it can do once connected.
Which MCP clients can connect?
Any client that speaks Streamable HTTP MCP. That includes Claude, Claude Code, Cursor, and Windsurf. The server implements the official Model Context Protocol SDK, so a new compliant client works without changes on our side.
What can the MCP tools do?
Read-only tools search the node catalog, fetch node details and workflow patterns, list and read workflows, and validate a workflow. Write tools create, update, and adopt workflows. A third group is flagged destructive because it touches production directly: executing a workflow to diagnose it, healing it, restoring a snapshot, and writing native changes. Every tool carries these annotations in the protocol, so your client can prompt you before the risky ones run.
Is the MCP server safe to point an autonomous agent at?
The tools call the same API boundary the web app uses, so workspace scoping, the allowlisted patch schema, and approval gates on native changes all apply. An agent cannot reach your n8n instance by any path that skips those checks.
Is MCP access included on the Basic plan?
Yes. MCP access is part of Basic, along with version history, validation, and rollback. The read-only tools and the workflow create and update tools work on Basic; the AI workflow builder and Guard's healing tools require AI Pro.