01 · ABOUT

What AuthPlane does

A self-hosted OAuth 2.1 authorization server for MCP servers.

Why teams reach for it: Replaces per-MCP-server user databases, consent UX, and session models with a single authorization server for identity, authorization, audience binding, revocation, and audit.

Worth knowing

Federates to Google Workspace, Okta, Entra ID, Auth0, or any OIDC provider rather than replacing them. SQLite for local use, PostgreSQL and Helm for production. A Token Vault holds per-user upstream credentials. Enterprise and cloud editions are stated as roadmap. This directory is built and maintained by AuthPlane; see the inclusion rule.

Self-hostedOpen SourceGoTypeScriptMCP Server
02 · TECHNICAL SPECIFICATIONS

How AuthPlane 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
Token Exchange (RFC 8693)
Yes
Agent Delegation
Carried in token
Idp Federation
OIDC
Upstream Token Vault
Yes
Self Hostable
Yes
Audit Log
Yes
03 · NEW TO MCP?
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.