Dynamic Client Registration (DCR)ΒΆ
Dynamic Client Registration (DCR) is an OAuth 2.0 extension that enables automatic client registration without manual configuration. This guide explains how to configure and use DCR with MCP Gateway for streamable HTTP servers.
OverviewΒΆ
DCR solves a common authentication challenge in distributed MCP deployments: - Traditional OAuth2 requires pre-configured client credentials for each MCP server - With DCR, MCP clients can automatically register themselves as OAuth2 clients
What is Dynamic Client Registration?ΒΆ
Dynamic Client Registration is defined in RFC 7591 as a protocol that allows OAuth 2.0 clients to register with authorization servers dynamically. In the context of MCP Gateway:
ArchitectureΒΆ
A simplified architecture. Please view the following guide for an in depth swimlane chart:
π Dynamic Client Registration with HyperMCP Tutorial
graph LR
Client[MCP Client]
HyprMCP[HyprMCP Gateway]
Dex[Dex]
IdP[Federated IdP<br/>GitHub/Google/LDAP]
ContextForge[ContextForge]
Client --> HyprMCP
HyprMCP --> Dex
Dex -.-> IdP
HyprMCP --> ContextForge
Related DocumentationΒΆ
- OAuth 2.0 Integration - General OAuth2 configuration
- Proxy Authentication - Using authentication proxies
- SSO Configuration - Single Sign-On setup
- Security Best Practices - Security guidelines