Data as of

n8n MCP Server for Cursor: Setup & Config

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

n8n MCP Server Cursor configuration

  1. Choose Cursor configuration scope

    For n8n MCP Server, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add n8n MCP Server to Cursor

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

  3. Check n8n MCP Server in Cursor

    n8n MCP Server: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.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 in Cursor: stdio checks

  • Cursor must find n8n-mcp-server for n8n MCP Server. Enable the project/user entry in MCP settings and inspect its tools.
  • Review N8N_API_KEY, N8N_API_URL for n8n MCP Server before sharing project .cursor/mcp.json; project scope travels with the repository.
  • n8n MCP Server uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
Tools
workflow_list, workflow_get, workflow_create

n8n MCP Server — details. Cursor guide

Frequently asked questions

Cursor's n8n MCP Server entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's n8n-mcp-server example uses stdio.

n8n MCP Server's Cursor configuration invokes n8n-mcp-server.

Cursor'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 Cursor's connected tool list; the stored list is not a live check.