A valid request URL is required to generate request examples{
"resource": "https://your-bifrost-domain.com/mcp",
"authorization_servers": [
"https://your-bifrost-domain.com"
],
"scopes_supported": [
"mcp:read",
"mcp:write"
],
"bearer_methods_supported": [
"header"
]
}Protected Resource Metadata (RFC 9728)
Returns the OAuth 2.0 Protected Resource Metadata document per RFC 9728.
MCP clients fetch this after receiving a 401 response from /mcp (with a
WWW-Authenticate: Bearer resource_metadata=".../.well-known/oauth-protected-resource"
header). The response tells the client which authorization server(s) protect the
/mcp resource so it can proceed with discovery.
Returns 404 when no MCP clients are configured with auth_type: per_user_oauth.
A valid request URL is required to generate request examples{
"resource": "https://your-bifrost-domain.com/mcp",
"authorization_servers": [
"https://your-bifrost-domain.com"
],
"scopes_supported": [
"mcp:read",
"mcp:write"
],
"bearer_methods_supported": [
"header"
]
}Documentation Index
Fetch the complete documentation index at: https://docs.getbifrost.ai/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Bearer token authentication. Use your provider API key or Bifrost authentication token.
Virtual keys (prefixed with sk-bf-) can also be passed here.
Response
Protected resource metadata
OAuth 2.0 Protected Resource Metadata per RFC 9728. Returned by /.well-known/oauth-protected-resource to tell MCP clients which authorization server(s) protect the /mcp endpoint.
URL of the protected resource (Bifrost's /mcp endpoint)
"https://your-bifrost-domain.com/mcp"
List of authorization server issuer URLs
["https://your-bifrost-domain.com"]Scopes supported by this resource
["mcp:read", "mcp:write"]Supported methods for passing Bearer tokens
["header"]Was this page helpful?

