Skip to content

Implement SEP-837: Specify OIDC application_type during Dynamic Client Registration #2783

Description

@stefanoamorelli

This issue tracks implementing SEP-837 in the client OAuth flow.

SEP-837 requires MCP clients to specify an application_type during OIDC Dynamic Client Registration. When it is omitted, OIDC-compliant authorization servers default the client to "web", which conflicts with the loopback (localhost, 127.0.0.1, ::1) redirect URIs that native clients (CLI and desktop apps) use, so the server can reject the registration.

Currently OAuthClientMetadata has no application_type field and create_client_registration_request never sends one, so the client hits exactly this default.

Spec: Application Type and Redirect URI Constraints

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status
    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions