Issue summary for n8n community post
Summary
I am trying to connect Claude Desktop on macOS to my n8n Cloud instance using the new MCP integration, but the connection fails immediately after initialization. The n8n Cloud MCP API key is valid and Claude Desktop detects the server, yet the MCP server repeatedly disconnects, so Claude cannot call any n8n tools. This makes it impossible to use n8n as a tool provider for Claude Desktop.
Environment
- macOS (desktop/laptop running Claude Desktop)
- Claude Desktop (latest version as of December 2025)
- n8n Cloud workspace (with MCP enabled and an instance‑level MCP API key)
- MCP connection configured as “n8n MCP” in Claude Desktop
What I expected - Claude Desktop should connect to the n8n MCP server using the API key from my n8n Cloud instance.
- After the initial handshake, Claude should list n8n tools and be able to trigger n8n workflows via MCP without disconnecting.
What happened - Claude tries to start the MCP server for n8n using the recommended
npx mcp n8n-mcpcommand. - The server appears to initialize, but then disconnects almost immediately with messages indicating the MCP server closed the connection.
- From the Claude side, the n8n MCP provider never becomes usable; tools are not available, and calls fail due to the disconnect.
- I repeated this multiple times with the same result, even after regenerating API keys and restarting Claude and the machine.
What I tried - Regenerated a new n8n MCP API key and updated the Claude Desktop MCP configuration.
- Restarted Claude Desktop and macOS.
- Verified that the n8n Cloud instance is reachable and that the API key works for other n8n API calls.
- Carefully followed the n8n MCP + Claude integration instructions and checked for obvious configuration errors.
- Captured logs and screenshots of the entire process and placed them in an attached PDF for reference.
Request - Can someone from the n8n team confirm whether the current n8n MCP server is expected to work with Claude Desktop on macOS using
npx mcp n8n-mcp? - If so, what additional configuration or troubleshooting steps should be taken to prevent the MCP server from disconnecting right after initialization?
- I have attached a PDF with detailed logs, screenshots, and the exact steps followed, with all API keys and tokens redacted.
Describe the problem/error/question
What is the error message (if any)?
Please share your workflow
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
Share the output returned by the last node
Information on my n8n setup
-
n8n version: n8n Cloud (current hosted version as of December 2025; exact version not shown in UI)
-
Database: n8n Cloud default (managed by n8n; not self‑hosted)
-
n8n EXECUTIONS_PROCESS setting: n8n Cloud default (not manually changed)
-
Running n8n via: n8n Cloud (hosted SaaS)
-
Operating system (for Claude Desktop client): macOS Ventura 13.7.8 (22H730)
