The n8n MCP server lets Claude trigger your self-hosted automation workflows. Think Zapier, but you own the infrastructure and the integrations. For anyone already running n8n, the MCP server turns every workflow into a prompt-triggerable action.
n8n’s strength is breadth: hundreds of integrations, full code nodes, branching logic. The MCP server gives Claude a way to invoke any of it.
Why use it
n8n shines when your automation gets complicated. Conditional branches, retries, custom code, weird API calls. The flip side: you usually trigger workflows from the n8n UI or a webhook, which means switching tools. The MCP server keeps everything in the conversation.
For solo founders running n8n as their automation backbone, this is what makes Claude the front-end for the whole stack. “Send this customer a follow-up email and add them to my CRM” becomes one prompt, even though the workflow under the hood touches three integrations.
What it actually does
The standard pattern: each n8n workflow exposes a webhook URL. The MCP server lets Claude POST to that URL with a JSON body, then read the response. More advanced servers expose the full n8n REST API for listing workflows, fetching execution history, and triggering by ID. Authentication is an n8n API key.
Practical patterns:
- “Trigger my ‘new lead’ workflow with this contact info.”
- “Run my ‘weekly digest’ workflow and tell me what the most recent execution returned.”
- “List all my n8n workflows and which ones have failed in the last 24 hours.”
Gotchas
Webhook URLs are sensitive. Anyone with the URL can trigger the workflow. Use n8n’s webhook auth options (header validation, basic auth) and don’t paste the raw URLs anywhere public.
Self-hosted n8n needs to be reachable from wherever the MCP server runs. If your client is on your laptop and n8n is on a private network, you’ll need a tunnel or a public-facing URL. Cloudflare Tunnel is a popular pattern for this.
Pair with Slack, Brevo, or Notion for the full stack: Claude triggers an n8n workflow, the workflow does the heavy lifting across N integrations, the result lands somewhere structured. The combination is more flexible than any single MCP server can offer.
For users who don’t want to self-host, Zapier is the hosted alternative. Less control, faster to set up, but you pay per task and you’re tied to their cloud.
