Claude can't sign in to AI Hub: discovery returns 404
I tried the new sign-in connection the day after the announcement, and again the next morning. On my white-label domain, Claude never reaches the sign-in page: it stops with an error saying it could not register with the sign-in service, so the connector stays disconnected. The token connection on the same address still works fine.
What happens today
In Claude, Customize → Connectors → Add custom connector, with my MCP address
https://<my-domain>/api/mcp. Claude detects that sign-in is required.Click Connect. Claude answers that it could not register with the sign-in service, and no sign-in page opens. Same result after deleting the connector and adding it again.
Looking at the server, the three OAuth discovery documents return the right JSON, but with HTTP status 404 instead of 200:
GET /.well-known/oauth-protected-resource/api/mcp -> 404 application/json (valid JSON body)
GET /.well-known/oauth-protected-resource -> 404 application/json (valid JSON body)
GET /.well-known/oauth-authorization-server -> 404 application/json (valid JSON body)
POST /oauth/register (empty body) -> 400 invalid_redirect_uri (endpoint is alive)
POST /register (empty body) -> 419My guess: Claude reads the 404 as "no metadata", falls back to the default /register path, and fails there. I can't confirm it from my side.
Proposal
Serve the three
.well-knowndocuments with status 200 on white-label domains.If it already works on other domains, check what differs on mine (happy to share the domain privately).
Log in to comment and vote
No comments yet
Be the first to share your thoughts.