Data as of
n8n MCP Server for VS Code: Setup & Config
n8n MCP Server lets VS Code manage workflows and inspect or control executions in an n8n instance.
n8n MCP Server VS Code configuration
Choose VS Code configuration scope
For n8n MCP Server, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.
Add n8n MCP Server to VS Code
Use the n8n-mcp-server entry below in servers. Keep n8n MCP Server's documented stdio connection fields and your other VS Code entries.
Check n8n MCP Server in VS Code
n8n MCP Server: Start in VS Code’s MCP controls; inspect output and trust prompts.
Config file · Workspace: .vscode/mcp.json
{
"servers": {
"n8n-mcp-server": {
"type": "stdio",
"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 VS Code: stdio checks
- Make n8n-mcp-server available in the workspace, container, or remote environment hosting n8n MCP Server. Start through VS Code's MCP controls; inspect output and trust prompts.
- For n8n MCP Server, keep N8N_API_KEY, N8N_API_URL out of version control; VS Code documents input variables and secret handling.
- n8n MCP Server uses stdio here: VS Code 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. VS Code guide
Frequently asked questions
For n8n MCP Server, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.
VS Code's n8n-mcp-server example uses stdio.
n8n MCP Server's VS Code configuration invokes n8n-mcp-server.
VS Code'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 VS Code's connected tool list; the stored list is not a live check.