Skip to content

Dynamic Client Registration on Guided OAuth Flow sending an empty body to endpoint #577

Open
@KKonstantinov

Description

@KKonstantinov

Describe the bug
When point 2 is reached on the Guided OAuth Flow, when debugging the incoming request, it can be observed that the inspector is sending an empty body to the endpoint.

For example, what claude sends is the following:

{
  "client_name": "claudeai",
  "grant_types": [
    "authorization_code",
    "refresh_token"
  ],
  "response_types": [
    "code"
  ],
  "token_endpoint_auth_method": "none",
  "scope": "claudeai",
  "redirect_uris": [
    "https://claude.ai/api/mcp/auth_callback"
  ]
}

To Reproduce
Steps to reproduce the behavior:

  1. Open up OAuth setup in Inspector
  2. Pass the first step successfully (Metadata Discovery) with both oauth-authorization-endpoint and oauth-protected-resource set up and no validation errors
  3. Attempt to pass the second step (Client Registration) and debug the body that is sent. If you're using a 3rd party auth server, modify the "registration_endpoint" inside the .well-known/oauth-authorization-endpoint to point to your own proxy endpoint and stop the debugger to see the request.

Expected behavior
Parameters sent as per the spec and generated as per the oauth-authorization-endpoint capabilities.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions