MCP server URL
https://prod-n8n.us-east-1.prod-services.fetchrewards.com/mcp-server/http
Where does the issue occur?
When pressing the Connect button
Transport used
streamable-http
Client registration type
Dynamic Client Registration (DCR)
SSE only: Does your server return the expected status code for POST requests?
Not sure
When did you last reproduce this?
2026-07-29 10:45 AM EST
Browser and OS
Chrome
Describe the issue
Couldn’t register with n8n MCP’s sign-in service. You can try again, or add an OAuth Client ID in the connector settings. If this persists, share this reference with support: “ofid_977b9c88bba79b05”
I entered my Oauth details into claude > organization settings > connectors > customer connector > web > n8n MCP and added the OAuth remote MCP server URL > then i attempted to connect and ran into the error above.
Issue details
Couldn’t register with n8n MCP’s sign-in service. You can try again, or add an OAuth Client ID in the connector settings. If this persists, share this reference with support: “ofid_977b9c88bba79b05”
Expected behavior
Immediate connection
Logs from your server
Additional context
No response
MCP server URL
https://prod-n8n.us-east-1.prod-services.fetchrewards.com/mcp-server/http
Where does the issue occur?
When pressing the Connect button
Transport used
streamable-http
Client registration type
Dynamic Client Registration (DCR)
SSE only: Does your server return the expected status code for POST requests?
Not sure
When did you last reproduce this?
2026-07-29 10:45 AM EST
Browser and OS
Chrome
Describe the issue
Couldn’t register with n8n MCP’s sign-in service. You can try again, or add an OAuth Client ID in the connector settings. If this persists, share this reference with support: “ofid_977b9c88bba79b05”
I entered my Oauth details into claude > organization settings > connectors > customer connector > web > n8n MCP and added the OAuth remote MCP server URL > then i attempted to connect and ran into the error above.
Issue details
Couldn’t register with n8n MCP’s sign-in service. You can try again, or add an OAuth Client ID in the connector settings. If this persists, share this reference with support: “ofid_977b9c88bba79b05”Expected behavior
Immediate connection
Logs from your server
Additional context
No response