Register an OAuth app via MCP discovery (dynamically registered client).

RegisterDiscoveredOAuthApp registers an OAuth app by discovering the
provider configuration from an MCP server URL (RFC 9728 + RFC 8414) and
dynamically registering a client with the provider authorization server
(RFC 7591). The resulting app row is identical in shape to CreateOAuthApp
plus discovery provenance. Fails with FailedPrecondition when the URL is
not an MCP-protected resource or the authorization server does not
support dynamic client registration.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The ID of the organization.

Body Params

Request message for registering an OAuth app via MCP discovery (DCR).

string
required

The ID of the organization.

string
required

Human-readable display name; unique per organization among live apps.
Also used as the client name presented on provider consent screens.

string
required

The MCP server URI to discover (absolute https URI). The service resolves
RFC 9728 protected-resource metadata and RFC 8414 authorization-server
metadata from it, then registers a client through the discovered DCR
endpoint (the client is a public PKCE client).
Example: https://mcp.atlassian.com/v1/mcp/authv2

hostPatterns
array of strings

The host patterns issued user tokens resolve for. Same semantics as in
CreateOAuthApp; must not overlap with another live app in the
organization.

hostPatterns
scopes
array of strings

Optional scope override. When empty, the scopes advertised in the
discovery metadata are used; an empty discovered set is permitted.

scopes
redirectUris
array of strings

Optional redirect URI whitelist override for the DCR registration. When
empty, the service's configured whitelist is registered.

redirectUris
Responses

Language
Credentials
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json