Fix guides · check compat.oauth_discovery

Publish OAuth metadata so MCP clients can sign in

Remote clients find your authorization server through RFC 9728 protected-resource metadata and RFC 8414 server metadata.

Why it matters

Without /.well-known/oauth-protected-resource (and the WWW-Authenticate resource_metadata pointer on 401), clients such as Claude cannot start the login flow and users are told the server is broken.

What to do

GET /.well-known/oauth-protected-resource
{ "resource": "https://api.example.com/mcp", "authorization_servers": ["https://auth.example.com"] }

Check your server

Paste your endpoint at /check, or run it in CI:

pipx run glimind check https://your-server.example.com/mcp --min-grade B

Related

• Support dynamic client registration for MCP clients