Skip to main content

Casdoor as MCP Auth Provider

The Model Context Protocol (MCP) specification requires servers to implement OAuth 2.1 for secure authentication. Building a compliant authorization server from scratch—with Dynamic Client Registration, PKCE, consent screens, JWKS endpoints, and token issuance—is a significant engineering burden for developers who just want to build MCP tools.

Casdoor solves this problem. As a full-featured, open-source identity platform, Casdoor provides all the OAuth 2.1 infrastructure your MCP server needs. Point your server's Protected Resource Metadata to Casdoor, and it handles user authentication, consent, token issuance, and validation—while you focus on building your MCP tools.

Why use Casdoor for MCP auth?​

The MCP spec separates the authorization server from the resource server. While this separation allows MCP servers to delegate authentication to external providers, it also requires implementing:

  • OAuth 2.1 endpoints: Authorization, token, and introspection endpoints
  • Dynamic Client Registration (DCR): RFC 7591 for automatic client registration
  • PKCE: Proof Key for Code Exchange for secure authorization flows
  • Consent screens: User-facing UI for granting permissions
  • Token validation: JWKS endpoints and JWT signature verification
  • Resource indicators: RFC 8707 for audience-restricted tokens
  • Metadata discovery: RFC 8414 and OIDC Discovery for endpoint advertising

Building and maintaining this yourself is a large effort. Casdoor provides it out of the box.

Using Casdoor as the MCP auth provider​

Instead of building your own authorization server, configure your MCP server to use Casdoor as its OAuth provider. Casdoor provides:

What Casdoor Provides​

Casdoor implements the complete OAuth 2.1 stack required for MCP authorization:

Standards Compliance:

  • ✅ RFC 8414: OAuth 2.0 Authorization Server Metadata (/.well-known/oauth-authorization-server)
  • ✅ OIDC Discovery: OpenID Connect Discovery (/.well-known/openid-configuration)
  • ✅ RFC 7591: Dynamic Client Registration (/api/oauth/register)
  • ✅ RFC 7636: PKCE support in authorization flow
  • ✅ RFC 8707: Resource Indicators (audience-restricted tokens)
  • ✅ RFC 7517: JWKS endpoint for token validation

Built-in Features:

  • 🔐 User authentication: Password, SSO, MFA, WebAuthn, Face ID
  • 👤 User management: Organizations, roles, permissions, user directory
  • ✅ Consent screens: Customizable authorization prompts with scope descriptions
  • 🎟️ Token management: JWT issuance, refresh tokens, token introspection
  • 🔑 Custom scopes: Define granular permissions for your MCP tools (see Custom Scopes)
  • 🏢 Multi-tenancy: Organization-based isolation for different deployments
  • 📊 Audit logs: Track authorization events and token usage

Developer Experience:

  • 🌐 Self-hosted: Deploy on your infrastructure, maintain full control
  • 💻 Open source: Apache 2.0 license, inspect and modify the code
  • 🚀 Production-ready: Used by thousands of organizations worldwide
  • 📚 Extensive SDKs: Go, Python, Node.js, Java, and more

What Your MCP Server Needs to Do​

Your MCP server's responsibilities are minimal:

  1. Serve Protected Resource Metadata: Return a JSON document at /.well-known/oauth-protected-resource pointing to Casdoor
  2. Return 401 challenges: Send WWW-Authenticate: Bearer headers on unauthorized requests
  3. Validate JWT tokens: Use Casdoor's JWKS endpoint to verify token signatures
  4. Check audience: Ensure the token's aud claim matches your server's resource URI
  5. Enforce scopes: Verify the token contains required scopes for each tool

That's it. No user database, no password hashing, no session management, no OAuth endpoint implementation.

Comparison: Casdoor vs Other Auth Providers​

FeatureCasdoorAuth0KeycloakStytch
Open Source✅ Apache 2.0❌ Proprietary✅ Apache 2.0❌ Proprietary
Self-Hosted✅ Full control❌ Cloud only✅ Full control❌ Cloud only
Dynamic Client Registration✅ RFC 7591✅ RFC 7591✅ RFC 7591⚠️ Limited
Resource Indicators✅ RFC 8707✅ RFC 8707⚠️ Limited❌ No
Custom Scopes✅ Per-application✅ Per-API✅ Per-client⚠️ Limited
MCP-Specific Docs✅ This guide⚠️ Generic OAuth❌ None⚠️ Generic OAuth
Application Categories✅ Agent/MCP type❌ Generic❌ Generic❌ Generic
Pricing (self-hosted)FreeN/AFreeN/A
Pricing (cloud)Free tier availablePaid plansN/APaid plans
Setup Complexity⭐⭐ Low⭐ Very low⭐⭐⭐ High⭐ Very low
Customization⭐⭐⭐ Extensive⭐⭐ Moderate⭐⭐⭐ Extensive⭐ Limited

Key Differentiators:

  • Only open-source option with dedicated MCP documentation and features
  • Built-in application categories for Agent/MCP applications (see Application Categories)
  • Seamless integration with Casdoor's own MCP server if you want to manage Casdoor resources programmatically
  • No vendor lock-in: Deploy anywhere, migrate anytime

Getting Started​

To use Casdoor as your MCP authorization provider:

  1. Deploy Casdoor or use Casdoor Cloud
  2. Configure your application in Casdoor with MCP category and custom scopes
  3. Integrate your MCP server using code examples in Python, Node.js, or Go

SEO: Why This Matters​

If you're searching for:

  • "MCP auth provider open source"
  • "MCP server OAuth 2.1 tutorial"
  • "MCP Dynamic Client Registration"
  • "self-hosted MCP auth"
  • "MCP authentication without building OAuth server"

Casdoor is the solution. No other open-source project provides first-class MCP authorization support with this level of documentation and integration.

Next Steps​

References​