Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.alpic.ai/llms.txt

Use this file to discover all available pages before exploring further.

Here is a list of popular Identity Providers (IdP) and their corresponding configuration endpoints. Those endpoints are public and contain informations that you’ll need to configure properly your MCP server OAuth protection.
OpenID Connect (OIDC) is a superset of OAuth 2.0 - if a platform is OIDC compliant, it’s OAuth 2.0 compliant.

​
OpenID Connect (OIDC) compliant Providers

These providers are popular IdPs compliant with OpenID Connect. You can use them as identity pools for your MCP server (meaning you don’t have to own yourself a database of users, you can instead simply gate access to your MCP server with these identity providers).
None of these providers have Dynamic Client Registration enabled. You’ll need to use Alpic DCR proxy in order to use them as valid identity providers for your MCP server.
Identity ProviderOpenID Connect Configuration Well-Known Endpoint
Applehttps://account.apple.com/.well-known/openid-configuration
Coinbasehttps://login.coinbase.com/.well-known/openid-configuration
Discordhttps://discord.com/.well-known/openid-configuration
Dropboxhttps://www.dropbox.com/.well-known/openid-configuration
Facebookhttps://www.facebook.com/.well-known/openid-configuration
Githubhttps://github.com/login/oauth/.well-known/openid-configuration
GitLabhttps://gitlab.com/.well-known/openid-configuration
Googlehttps://accounts.google.com/.well-known/openid-configuration
Hugging Facehttps://huggingface.co/.well-known/openid-configuration
Kakaohttps://kauth.kakao.com/.well-known/openid-configuration
Linehttps://access.line.me/.well-known/openid-configuration
LinkedInhttps://www.linkedin.com/oauth/.well-known/openid-configuration
Microsofthttps://login.microsoftonline.com/common/v2.0/.well-known/openid-configuration
Salesforcehttps://login.salesforce.com/.well-known/openid-configuration
Slackhttps://slack.com/.well-known/openid-configuration
Spotifyhttps://accounts.spotify.com/.well-known/openid-configuration
Twitchhttps://id.twitch.tv/oauth2/.well-known/openid-configuration
Xerohttps://identity.xero.com/.well-known/openid-configuration

​
Identity Management Platforms

You’ll find below the most popular IdPs compliant with OAuth 2.1. You can use them to provision your own user pools for your MCP server.
Identity Management PlatformOpenID Connect Configuration Well-Known Endpoint
Auth0https://{tenant}.us.auth0.com/.well-known/openid-configuration
Amazon Cognitohttps://cognito-idp.{region}.amazonaws.com/{user-pool-id}/.well-known/openid-configuration
Clerkhttps://{tenant}.clerk.accounts.dev/.well-known/openid-configuration
Google Identity Platform (formerly Firebase Authentication)https://securetoken.google.com/{tenant}/.well-known/openid-configuration
Logtohttps://{tenant}.logto.app/.well-known/openid-configuration
Microsoft Entra ID (formerly Azure AD)https://login.microsoftonline.com/{tenant}/v2.0/.well-known/openid-configuration
Oktahttps://{tenant}.okta.com/.well-known/openid-configuration
Stytchhttps://{tenant}.customers.stytch.com/.well-known/openid-configuration
WorkOShttps://{tenant}.authkit.app/.well-known/openid-configuration
You might want to try https://{your - domain}/.well-known/openid-configuration instead of the provider specific URL if a custom domain has been setup on your Identity Management Platform.

​
Other Identity Providers

You can use any IdP to configure authorization on your MCP server. Use the login page domain to discover /.well-known/oauth-authorization-server endpoint. For exemple, you can login to Box using https://account.box.com/login. Box’s OAuth Authorization Server metadata endpoint is https://account.box.com/.well-known/oauth-authorization-server