Claude web custom connector is available in the web version of Claude. They require OAuth2-compatible auth on the MCP Server Trigger so it can be used as a remote MCP connector (not just via local desktop gateways). Since Claude now supports connectors through the web version of Claude Chat, it would be useful to add this feature to the roadmap.
The idea is:
Creating an MCP Server Trigger node in a workflow would enable OAuth authentication, similar to how authentication is handled at the instance-level MCP server.
My use case:
The key use case is enabling Claude on the web to discover and directly trigger all tools connected to the MCP Server Trigger node.
I think it would be beneficial to add this because:
The current MCP Server Trigger node works great for local desktop connections via Claude Desktop, but as soon as you want Claude.ai (web) to call it as a remote MCP connector, you hit the OAuth requirement wall. The web version requires OAuth 2.0 with dynamic client registration, and the trigger node does not expose that.
The workaround I have been using is running a lightweight OAuth proxy in front of the n8n webhook — basically a small Express server that handles the OAuth flow and forwards authenticated requests to the n8n webhook URL. It works but it is annoying overhead that should not be necessary.
The ideal solution would be exactly what you described — OAuth 2.0 support baked into the MCP Server Trigger node, similar to how the instance-level MCP server handles authentication. If n8n can expose /.well-known/oauth-authorization-server and handle dynamic client registration per-trigger, Claude web connectors would work out of the box.
Upvoted. This would unlock a huge use case — any n8n workflow could become a first-class Claude web tool without custom server infrastructure.