Is github mcp serve with oauth supposed to be working? #5716

Activity

1. github-actions

   assigned

   rekram1-node

   on Dec 18, 2025
2. github-actions commented on Dec 18, 2025

   

   github-actionsBot

   on Dec 18, 2025 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • MCP with oauth doesn't work #5444: MCP with oauth doesn't work - User experiencing similar issue where OAuth-enabled MCP servers are not being recognized, with the same "No OAuth-enabled MCP servers configured" error message when trying to authenticate.

   Feel free to ignore if none of these address your specific case.
3. christso commented on Dec 28, 2025

   

   christso

   on Dec 28, 2025

   Contributor

   More actions

   You're just missing the Authorization header. Add a Personal Access Token (fine-grained or classic):

   "github": {
     "type": "remote",
     "url": "https://api.githubcopilot.com/mcp/",
     "headers": {
       "Authorization": "Bearer ghp_your_token_here",
       "X-MCP-Toolsets": "repos,issues",
       "X-MCP-Readonly": "true"
     }
   }

   The HTTP 422 error is because GitHub doesn't support Dynamic Client Registration. Once PR #5940 is merged, you'll be able to use OAuth by configuring your own clientId/clientSecret - which is the recommended approach.
4. thdxr commented on Mar 25, 2026

   

   thdxr

   on Mar 25, 2026

   Member

   More actions

   To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
5. sheldonhull

   closed this as not plannedon Apr 5, 2026