Issue with connect n8n mcp to claude routine

Questions
1

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

Today I updated the n8n Cloud instance to the latest stable version. Until yesterday night, the n8n MCP integration with Claude was working perfectly.

However, after today’s update, the MCP connection stopped working. Claude now shows an MCP permission/authorization issue from the n8n server side.
I already:

  • checked all MCP settings,
  • verified permissions,
  • disconnected and reconnected multiple times,
  • restarted the connection flow,
    but the same error still appears.
    What is the correct solution to reconnect n8n MCP with Claude after the latest n8n update? Is this a known issue with the new stable release or MCP authentication changes?

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Welcome to the n8n community @Gaurav_V

It would be important to share the exact error displayed in Claude, the current version of n8n Cloud, and whether the MCP endpoint/token was recreated after the update. Without this I can’t help

3

Welcome @Gaurav_V to our community! I’m Jay and I am a n8n verified creator.

What’s the exact error message Claude shows when it tries to connect? Also - in your Claude MCP config, can you confirm the URL still matches the MCP server URL shown in your n8n MCP Server Trigger node? After a Cloud update, n8n sometimes regenerates the webhook base URL. Open the MCP Trigger node in n8n, copy the URL it shows, and update your Claude mcpServers config with the fresh URL. That’s the most common cause after an update.

4

@Gaurav_V If the auth issues persist after the update, there’s an alternative approach that avoids the n8n built-in MCP entirely. I built a Python MCP server that connects Claude to n8n over stdio using the n8n REST API directly; no OAuth, no webhook URLs to maintain. Might be worth a try if you can’t get the native connection stable: https://github.com/DerJams/n8n-mcp-server-python