Repository navigation
HTTP 405 trying to load well-known OAuth metadata #634
Description
Describe the bug
When attempting to walk through the auth flow for my server, I get the following:
HTTP 405 trying to load well-known OAuth metadata
This seems to be directly related to: modelcontextprotocol/typescript-sdk#744
To Reproduce
Steps to reproduce the behavior:
- Have an OAuth server in the protected metadata at a trailing path like so:
my-org.okta.com/oauth/abc123 - Attempt to walk through OAuth
- Notice error
- Open console and see the following:
OAuth flow error: Error: HTTP 405 trying to load well-known OAuth metadata
discoverOAuthMetadata http://localhost:6274/assets/index-CPgI0-gs.js:16611
Expected behavior
OAuth flow to work with any auth server provider
Reacted by Franz and John Stillwagen
Activity
tomekchime commentedon Aug 9, 2025
Hmm, it looks like modelcontextprotocol/typescript-sdk#652 added OIDC Discovery support and version 0.16.2 pulled in that update, but this bug still exists in inspector.
sbbeez commentedon Oct 4, 2025
I see the PR is already up to fix it.
Faced this issue when using okta as authorization server, for temporary fix,
urlsToTryinbuildDiscoveryUrlsfunction, updated last one to firstnpm run devfrom the repo instead of inspector commandAdding this, just in case someone is facing this issue
olaservo commentedon Oct 13, 2025
Hi @sbbeez, I see you mentioned a PR here, could you link to which PR you're referring to related to resolving this issue? Thanks!
olaservo commentedon Jan 18, 2026
This should be fixed by PR #702. Closing - please reopen if you're still experiencing this issue.
This comment was posted by Claude during issue triage.