After upgrading to 1.93.0, claude desktop cannot connect to MCP properly

[sunybgit]

Bug Description

After upgrading to 1.93.0, claude desktop cannot connect to n8n MCP

2025-05-26T13:05:05.940Z [n8n-TEST] [info] Initializing server...
2025-05-26T13:05:06.043Z [n8n-TEST] [info] Server started and connected successfully
2025-05-26T13:05:06.046Z [n8n-TEST] [info] Message from client: {"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0}
[supergateway] Starting...
[supergateway] Supergateway is supported by Supermachine (hosted MCPs) - https://supermachine.ai
[supergateway] - outputTransport: stdio
[supergateway] - sse: https://realtorapp.app.n8n.cloud/mcp/066ed9b4-acee-4f07-a5bf-d1c5889d8674/sse
[supergateway] - Headers: (none)
[supergateway] Connecting to SSE...
[supergateway] Stdio server listening
[supergateway] Stdio → SSE: {
jsonrpc: '2.0',
id: 0,
method: 'initialize',
params: {
protocolVersion: '2024-11-05',
capabilities: {},
clientInfo: { name: 'claude-ai', version: '0.1.0' }
}
}
[supergateway] SSE connected
[supergateway] Response: {
jsonrpc: '2.0',
id: 0,
result: {
protocolVersion: '2025-03-26',
capabilities: { tools: {} },
serverInfo: { name: 'n8n-mcp-server', version: '0.1.0' }
}
}
2025-05-26T13:05:19.264Z [n8n-TEST] [info] Message from server: {"jsonrpc":"2.0","id":0,"result":{"protocolVersion":"2025-03-26","capabilities":{"tools":{}},"serverInfo":{"name":"n8n-mcp-server","version":"0.1.0"}}}
2025-05-26T13:05:19.277Z [n8n-TEST] [info] Client transport closed
2025-05-26T13:05:19.278Z [n8n-TEST] [info] Server transport closed
2025-05-26T13:05:19.278Z [n8n-TEST] [info] Client transport closed
2025-05-26T13:05:19.278Z [n8n-TEST] [info] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. console.error('...') in JavaScript, print('...', file=sys.stderr) in python) and it will appear in this log.
2025-05-26T13:05:19.278Z [n8n-TEST] [error] Server disconnected. For troubleshooting guidance, please visit our debugging documentation {"context":"connection"}
[supergateway] stdin closed. Exiting...
2025-05-26T13:05:19.308Z [n8n-TEST] [info] Server transport closed
2025-05-26T13:05:19.308Z [n8n-TEST] [info] Client transport closed

To Reproduce

run claude desktop

Expected behavior

connected

Operating System

cloud

n8n Version

1.93.0

Node.js Version

20

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @sunybgit,

We have created an internal ticket to look into this which we will be tracking as "GHC-2187"

[that0n3guy]

This is true for 1.94.1 as well (thats what I'm running)

Putting the community link here as well: https://community.n8n.io/t/mcp-server-n8n-cloud-not-working-in-claude-desktop/118647

[that0n3guy]

I'm also having this issue. Everything from claude to n8n mcp server trigger was wroking fine but an upgrade to 1.94.1 from ~1.92 and its not working now.

My claude desktop logs:

2025-05-29T13:33:39.684Z [AmazingMarvin] [info] Initializing server...
2025-05-29T13:33:39.701Z [AmazingMarvin] [info] Server started and connected successfully
2025-05-29T13:33:39.707Z [AmazingMarvin] [info] Message from client: {"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0}
[supergateway] Starting...
[supergateway] Supergateway is supported by Supermachine (hosted MCPs) - https://supermachine.ai
[supergateway]   - outputTransport: stdio
[supergateway]   - sse: https://***.com/mcp/***/sse
[supergateway]   - Headers: {"Authorization":"Bearer ****"}
[supergateway] Connecting to SSE...
[supergateway] Stdio server listening
[supergateway] Stdio → SSE: {
  jsonrpc: '2.0',
  id: 0,
  method: 'initialize',
  params: {
    protocolVersion: '2024-11-05',
    capabilities: {},
    clientInfo: { name: 'claude-ai', version: '0.1.0' }
  }
}
[supergateway] SSE connected
[supergateway] Response: {
  jsonrpc: '2.0',
  id: 0,
  result: {
    protocolVersion: '2025-03-26',
    capabilities: { tools: {} },
    serverInfo: { name: 'n8n-mcp-server', version: '0.1.0' }
  }
}
2025-05-29T13:33:51.291Z [AmazingMarvin] [info] Message from server: {"jsonrpc":"2.0","id":0,"result":{"protocolVersion":"2025-03-26","capabilities":{"tools":{}},"serverInfo":{"name":"n8n-mcp-server","version":"0.1.0"}}}
2025-05-29T13:33:51.291Z [AmazingMarvin] [info] Client transport closed
2025-05-29T13:33:51.291Z [AmazingMarvin] [info] Server transport closed
2025-05-29T13:33:51.291Z [AmazingMarvin] [info] Client transport closed
2025-05-29T13:33:51.292Z [AmazingMarvin] [info] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. `console.error('...')` in JavaScript, `print('...', file=sys.stderr)` in python) and it will appear in this log.
2025-05-29T13:33:51.292Z [AmazingMarvin] [error] Server disconnected. For troubleshooting guidance, please visit our [debugging documentation](https://modelcontextprotocol.io/docs/tools/debugging) {"context":"connection"}
[supergateway] stdin closed. Exiting...
2025-05-29T13:33:51.308Z [AmazingMarvin] [info] Server transport closed
2025-05-29T13:33:51.308Z [AmazingMarvin] [info] Client transport closed

@Joffcom I think there are a bunch of duplicates on this:

#15572
#15831

[jeanpaul]

Hey, it seems that supergateway has some issues (see also here)

I’ve now switched to mcp-remote and that resolved my issues. The MCP config in Claude Desktop now looks like this:

{
  "mcpServers": {
    "n8n": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "<URL>",
        "--header",
        "Authorization: Bearer ${AUTH_TOKEN}"
      ],
      "env": {
        "AUTH_TOKEN": "<TOKEN>"
      }
    },
  }
}

Please let me know if this resolves your issues!

[guix54]

Hello @Joffcom
seems to be efficient on my localhost...Thanks a lot!!!

[that0n3guy]

Hey, it seems that supergateway has some issues (see also here)

I’ve now switched to mcp-remote and that resolved my issues. The MCP config in Claude Desktop now looks like this:

Seems to work, thanks!