What Scalekit MCP Auth does
Drop-in OAuth 2.1 for any MCP server — user login, SSO, agent tokens, scopes, and DCR included
Why teams reach for it: Provides MCP-specific authorization endpoints without modifying an existing application's own auth stack.
Worth knowing
It implements OAuth 2.1, with PKCE required, and CIMD and DCR client registration. It federates with Okta, Microsoft Entra ID, ADFS and holds an upstream token vault for third-party credentials and is self-hostable.
How Scalekit MCP Auth compares
Fields the vendor doesn't document are left blank here rather than guessed — a blank means nothing verified, not a "no."
- Oauth Version
- OAuth 2.1
- Client Registration
- CIMD and DCR
- Resource Indicators (RFC 8707)
- Yes
- Protected Resource Metadata (RFC 9728)
- Yes
- Authorization Server Metadata (RFC 8414)
- Yes
- Pkce
- Required
- Agent Delegation
- Carried in token
- Idp Federation
- Okta, Microsoft Entra ID, ADFS
- Upstream Token Vault
- Yes
- Self Hostable
- Yes
- Audit Log
- Yes
Who can connect, and what may they do?
Authorization & identity tools control who — or which AI agent — is allowed to connect, and what they're allowed to do once connected.