n8n MCP Server — Build Automations with AI, 1,396 Nodes

What it is

n8n MCP Server is a bridge between AI assistants and the n8n workflow automation platform. It exposes 1,396 n8n nodes (812 core plus 584 community) and 2,709 workflow templates as MCP tools that any compatible AI agent can call. Instead of manually dragging and dropping nodes in the n8n canvas, developers describe what they want in plain English and the AI builds the workflow.

The server targets automation engineers and developers who already use n8n and want AI-assisted workflow creation. It works with Claude Code, Claude Desktop, Cursor, and Windsurf.

How it saves time or tokens

Manually building an n8n workflow requires reading documentation for each node, understanding trigger types, and wiring data transformations. The MCP server pre-loads 87% documentation coverage so the AI agent can answer questions like 'What Slack actions are available in n8n?' without the user searching docs. The agent constructs valid workflow JSON directly, eliminating trial-and-error in the visual editor.

Because node documentation is served on demand through MCP tools rather than stuffed into a system prompt, token usage stays low -- the agent fetches only the docs it needs for the current task.

How to use

1. Run directly with npx (no install required):

npx n8n-mcp

1. Or add to your MCP client config:

{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": ["-y", "n8n-mcp"]
    }
  }
}

1. Restart your AI tool and start requesting automations in natural language.

Example

User: Create an n8n workflow that watches a Gmail inbox for emails
      with 'invoice' in the subject, extracts the PDF attachment,
      and uploads it to Google Drive.

Agent (via n8n MCP): Here is the workflow JSON with three nodes:
  1. Gmail Trigger (filter: subject contains 'invoice')
  2. Extract attachment (binary data)
  3. Google Drive Upload (target folder: /Invoices)

The agent generates valid n8n workflow JSON that can be imported directly into your n8n instance.

Related on TokRepo

• Automation tools -- Browse more workflow automation resources on TokRepo
• AI tools for automation -- Complementary automation tools that pair well with n8n

Common pitfalls

• Running npx without a working n8n instance -- the MCP server generates workflow definitions, but you still need a running n8n server to execute them.
• Expecting community nodes to have the same documentation coverage as core nodes -- 87% coverage applies to the full set, but some community nodes have minimal docs.
• Not pinning the npx version in CI environments -- always specify a version to avoid breaking changes.