# context_server: Mirror authorization server grant_types_supported \(\#53501\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/79f998a5f3bcc0e1273121d061905c8b379a1f05)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 79f998a5f3bcc0e1273121d061905c8b379a1f05

Requested commit: 79f998a5f3bcc0e1273121d061905c8b379a1f05

Commit: 79f998a5f3bcc0e1273121d061905c8b379a1f05

Tree: 96f160841ed84ec2848f8d38b4baa1bc0283a407

Author: Tom Houlé

Committer: GitHub

## Message

```
context_server: Mirror authorization server grant_types_supported (#53501)

In MCP OAuth, mirror the authorization server's grant_types_supported in
the DCR registration body instead of hardcoding just authorization_code.
Logfire's auth server requires both authorization_code and refresh_token
in grant_types, and we already uses refresh tokens, so the only issue
was not advertising the capability during registration. The DCR body now
intersects our supported grant types with what the server advertises, or
sends all of ours when the server metadata omits grant_types_supported.

Without this change, the Pydantic Logfire MCP auth server refuses our
client registration.

Release Notes:

- MCP: Improve selection of the `grant_types` we send during OAuth
dynamic client registration.
```

## Parents

- [770e20c8390f9b12ef50fb84792c7b6ea7d654aa](https://git.cafe/gitcafe/zed/commit/770e20c8390f9b12ef50fb84792c7b6ea7d654aa?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/79f998a5f3bcc0e1273121d061905c8b379a1f05?format=markdown)