Thanks so much for putting this thread together. I noticed there might be two conversations happening in this thread at once.
One is allowing n8n to connect to other MCPs via OAuth (like Notion) from the MCP tool which looks like it just got released in n8n@1.119.0 (PR here).
The other though is how to authenticate workflows triggered by MCP so that we can leverage n8n as a go-between and trigger workflows from something like ChatGPT (which require OAuth).
I myself was mixing both up so posting this in case it clears it up for anyone else. Do we know if thereās any movement on the second use case Iāve mentioned above?
Yes! this exact use case of calling n8n via ChatGPT would be a major unlock. They really need to add OAuth support to their MCP Server node. Hoping for some movement on this.
Iām mainly concerned with supporting Oauth via the MCP Server Trigger Node.
The reason is simple. I want to expand Claude and ChatGPTās capabilities by connecting my N8N custom MCP tools to them . However, they only support oAuth based auth. I donāt even care about multi-tenant, audit-trails, etc. Just want to be able to create servers that work with standard MCP clients.
Using my first ever post on this community to say I want this as well please. OAuth is the go to standard for authenticating MCP and should be an option on N8Nās MCP node.
For reference this is the standard now:
In my opinion continuing to not support this and not depreciating the node therefore removing MCP functionality from N8N is potentially misleading as security best practice has moved on and users on N8N may reasonably assume that best practice is being followed when in this case it is not. Hence this is a security breach waiting to happen for users relying on the authentication methods offered.