1. Home
  2. n8n MCP Server
  3. n8n MCP Server for Claude Desktop: Setup & Config

Data as of

n8n MCP Server for Claude Desktop: Setup & Config

n8n MCP Server lets Claude Desktop manage workflows and inspect or control executions in an n8n instance.

What you can do with n8n in Claude Desktop

Pick it for workflow lifecycle controls, execution inspection, and webhook triggers against your n8n instance.

  • Create and update n8n workflows from an AI assistant.
  • Activate or deactivate existing automations.

Before you start: n8n in Claude Desktop

  • Node.js 20 or newer
  • An n8n instance with API access enabled
  • The globally installed @leonardsellem/n8n-mcp-server package
  • An n8n API key

Install with npm install -g @leonardsellem/n8n-mcp-server before using this executable. N8N_WEBHOOK_USERNAME and N8N_WEBHOOK_PASSWORD are needed only for webhook tools. Source builds and Docker are documented alternatives.

n8n Claude Desktop configuration

  1. Choose Claude Desktop configuration scope

    For n8n MCP Server, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

  2. Add n8n MCP Server to Claude Desktop

    Use the n8n-mcp-server entry below in mcpServers. Keep n8n MCP Server's documented stdio connection fields and your other Claude Desktop entries.

  3. Check n8n MCP Server in Claude Desktop

    n8n MCP Server: Fully quit and reopen Claude Desktop; check developer diagnostics.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

JSON
{
  "mcpServers": {
    "n8n-mcp-server": {
      "command": "n8n-mcp-server",
      "args": [],
      "env": {
        "N8N_API_URL": "<Full n8n API URL including /api/v1>",
        "N8N_API_KEY": "<n8n API key with appropriate permissions>"
      }
    }
  }
}

n8n tools available to Claude Desktop

n8n's stored tool list documents 12 tools; compare it with Claude Desktop's connected tool list, because the stored list is not a live check.

workflow_list

When Claude Desktop requests workflow_list from n8n, review the action before approving it.

Enumerate workflows in the connected n8n instance.

workflow_get

When Claude Desktop requests workflow_get from n8n, review the action before approving it.

Read one workflow’s configuration and details.

workflow_create

When Claude Desktop requests workflow_create from n8n, review the action before approving it.

Create a workflow definition.

workflow_update

When Claude Desktop requests workflow_update from n8n, review the action before approving it.

Change an existing workflow definition.

workflow_delete

When Claude Desktop requests workflow_delete from n8n, review the action before approving it.

Remove a workflow.

workflow_activate

When Claude Desktop requests workflow_activate from n8n, review the action before approving it.

Enable a workflow.

workflow_deactivate

When Claude Desktop requests workflow_deactivate from n8n, review the action before approving it.

execution_run

When Claude Desktop requests execution_run from n8n, review the action before approving it.

run_webhook

When Claude Desktop requests run_webhook from n8n, review the action before approving it.

execution_get

When Claude Desktop requests execution_get from n8n, review the action before approving it.

execution_list

When Claude Desktop requests execution_list from n8n, review the action before approving it.

execution_stop

When Claude Desktop requests execution_stop from n8n, review the action before approving it.

n8n: full stored tool descriptions

Troubleshooting n8n in Claude Desktop

  • Fully quit and reopen Claude Desktop for n8n MCP Server. If n8n-mcp-server is missing, check the desktop process's PATH, which may differ from your terminal.
  • In Claude Desktop's n8n MCP Server entry, check N8N_API_KEY, N8N_API_URL. Keep secrets out of shared screenshots and repositories.
  • n8n MCP Server uses stdio here: Claude Desktop must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Requires an API-enabled n8n instance and suitable API credentials.
  • Known limitation: Webhook use needs a configured workflow and Basic Authentication credentials.
  • Known limitation: The README describes part-time maintenance and a search for co-maintainers.
  • General Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

n8n MCP Server — details. Claude Desktop guide

Frequently asked questions

Claude Desktop loads n8n MCP Server from claude_desktop_config.json: ~/Library/Application Support/Claude/ on macOS, or %APPDATA%\Claude\ on Windows. Open it via Settings → Developer → Edit Config when available.

Claude Desktop's n8n-mcp-server example uses stdio.

n8n MCP Server's Claude Desktop configuration invokes n8n-mcp-server.

Claude Desktop's n8n MCP Server example references N8N_API_KEY, N8N_API_URL. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

n8n MCP Server's stored list contains 12 tools, including workflow_list, workflow_get, workflow_create. Compare those names with Claude Desktop's connected tool list; the stored list is not a live check.

Yes. The listed tools create, update, delete, activate, and deactivate workflows.

Configure Basic Authentication on the n8n webhook node and set N8N_WEBHOOK_USERNAME and N8N_WEBHOOK_PASSWORD on the server.