Can LiteLLM MCP Gateway connect to GitHub Copilot MCP using OAuth 2.1 + DCR instead of PAT?

[Sanady]

I’m trying to add the official GitHub Copilot MCP server to LiteLLM MCP Gateway through the LiteLLM UI.

The remote MCP server URL is:

https://api.githubcopilot.com/mcp/

I want to avoid using a GitHub PAT and instead use the OAuth flow, ideally OAuth 2.1 with Dynamic Client Registration (DCR).

GitHub’s documentation and changelog suggest enhanced MCP OAuth support and DCR support, but I’m not sure how this should be configured specifically in LiteLLM.

In LiteLLM UI, I tried configuring the MCP server with:

Authentication: OAuth
Authorization URL Override: https://github.com/login/oauth/authorize
Token URL Override: https://github.com/login/oauth/access_token

I also checked the metadata from:

https://api.githubcopilot.com/.well-known/oauth-protected-resource/mcp

However, during the authorization flow, LiteLLM returns errors such as:

{"detail": "MCP server authorization url is not set"}

or:

{"detail": "invalid_request"}

Questions

1. Does LiteLLM currently support connecting to GitHub Copilot MCP using OAuth 2.1 with Dynamic Client Registration?
2. If yes, what exact LiteLLM UI fields should be configured for:
   • MCP server URL
   • authorization URL
   • token URL
   • registration URL
   • client ID / client secret
   • callback / redirect URI
3. If DCR is not supported in this setup, is the only OAuth option to pre-register a GitHub OAuth App or GitHub App and manually provide the client ID and client secret?
4. Is PAT currently the only fully working authentication method for GitHub Copilot MCP behind LiteLLM?

I’m looking for the recommended production setup for GitHub Copilot MCP through LiteLLM without using PAT-based authentication.