Register and manage OAuth 2.0 clients for MCP servers
When a server uses ezforge_managed auth, client applications must register as OAuth clients before they can request tokens. This follows RFC 7591 (Dynamic Client Registration).Required scope: Session authentication only.
Registers a new OAuth client for the server.Request body:
{ "name": "My MCP Client", "redirectUris": ["https://myapp.example.com/callback"], "scopes": ["mcp:read"]}
Field
Type
Required
Description
name
string
✓
Human-readable client name (max 255 chars)
redirectUris
string[]
✓
One or more redirect URIs. Must use https except for loopback addresses (localhost, 127.0.0.1, [::1]). No fragment component (RFC 6749 §3.1.2). Max 20 entries.
scopes
string[]
—
Requested scopes. Defaults to ["mcp:read"] if omitted.