// DOCS
OAuth discovery for the AppHitlist MCP server
Clients connect to the AppHitlist MCP server with OAuth or with an API key as a bearer token.
Clients connect with OAuth or with an API key sent as a bearer token. The protected-resource document includes authorization_servers for this origin. Send the token on the Authorization header.
Protected resource metadata
Fetch https://apphitlist.com/.well-known/oauth-protected-resource/api/mcp. The same document is also served at https://apphitlist.com/.well-known/oauth-protected-resource.
{
"resource": "https://apphitlist.com/api/mcp",
"authorization_servers": [
"https://apphitlist.com"
],
"scopes_supported": [
"mcp"
],
"resource_name": "AppHitlist MCP",
"resource_documentation": "https://apphitlist.com/",
"bearer_methods_supported": [
"header"
]
}A request with no key, or a key that does not match, is rejected with HTTP 401. The challenge points at the protected-resource path above. Create a key on the API key page and send it as a bearer token.
- API key setup — Create the bearer key this document describes.
- MCP server — Tools and limits.