github
Remote: Incompatibility with Claude (Web) Integrations
Describe the bug
Setting up the remote GitHub MCP Server hosted at https://api.githubcopilot.com/mcp/ under https://claude.ai/settings/integrations leads to following issues:
- even after entering the URL with a trailing slash, Claude corrects it to https://api.githubcopilot.com/mcp
- upon clicking the "Connect" button Claude Code shows the error message "There was an error connecting to GitHub server. Please check your server URL and make sure your server handles auth correctly."
No other error message is shown, no more details are provided. The integration does not change into the "connected" mode.
Affected version
- the remote GitHub MCP Server hosted at https://api.githubcopilot.com/mcp/
Steps to reproduce the behavior
- open https://claude.ai/settings/integrations
- log in to Claude, if not logged in
- click "Add integration"
- enter "Integration name": GitHub
- enter "Integration URL": https://api.githubcopilot.com/mcp/
- click "Add"
- locate the "GitHub" integration in the list of integrations
- click "Connect"
Expected vs actual behavior
I expected the connection to be established, and asked for credentials, potentially by being redirected to the GitHub website.
Instead I got an error message reading "There was an error connecting to GitHub server. Please check your server URL and make sure your server handles auth correctly."
Logs
No logs are available.
The error is clearer when you attempt to add it to Claude Code. It complains of Dynamic client registration failing.
Good clue, but Claude Code and Claude Web use different MCP client implementations. Claude Web gets confused when MCP tool calls don't return a content array, Claude Code takes whatever else is in the result.
It wont work even if you force it to not remove the trailing slash by adding a placeholder query parameter such as https://api.githubcopilot.com/mcp/?placeholder=
Same here. Claude code doesnt seem to work with remote github mcp server
Actually I believe this is mainly an issue with Claude in general (Claude Code, Claude Desktop and Claude.ai) It only supports dynamic registration. I have my oauth2 MCP server that works neatly with VSCode and doesn't require dynamic registration.
IMO Claude team should consider changing their remote MCP integration to simpler implementation VSCode uses today.
Seeing the same issue as well. The native Github integration doesn't expose the MCP server and you cannot manually add the remote MCP.
It’s in the docs: Dynamic Client Registration is not supported at the moment. You have to use a PAT for Claude Code.
OAuth works only on MCP hosts that do not require Dynamic Client Registration.
Actually I believe this is mainly an issue with Claude in general (Claude Code, Claude Desktop and Claude.ai) It only supports dynamic registration. I have my oauth2 MCP server that works neatly with VSCode and doesn't require dynamic registration.
IMO Claude team should consider changing their remote MCP integration to simpler implementation VSCode uses today.
@mculp "Authorization servers and MCP clients SHOULD support the OAuth 2.0 Dynamic Client Registration Protocol (RFC7591)." the DCRP support is documented in the official model context protocol document, it's not the issue of Claude, but the github mcp server don't fully impl the mcp oauth flow. for detail, see: https://modelcontextprotocol.io/specification/draft/basic/authorization
I had the exact same issue in gemini-cli but I thought the issue was on gemini-cli's side. I created this ticket https://github.com/google-gemini/gemini-cli/issues/5011. The developer over there came to the same conclusion that GitHub's remote MCP endpoint does not support the OAuth 2.0 Dynamic Client Registration Protocol.
@trieloff, currently Claude Web (chat.claude.ai in the browser) does not support connecting to MCP servers. We would be happy to enable the GitHub server there one they do!
MCP support today is only in Claude Desktop (Mac + Windows apps) and Claude Code, which can host or connect to MCP servers via local or remote transports. I recommend opening an issue or discussion in the modelcontextprotocol organization for this request.
For folks with issues connecting to Claude Code or Claude Desktop, please open another ticket for better triaging.
@trieloff, currently Claude Web (chat.claude.ai in the browser) does not support connecting to MCP servers. We would be happy to enable the GitHub server there one they do!
MCP support today is only in Claude Desktop (Mac + Windows apps) and Claude Code, which can host or connect to MCP servers via local or remote transports. I recommend opening an issue or discussion in the modelcontextprotocol organization for this request.
This is incorrect. Chat.claude.ai does support Remote MCPs.
https://support.anthropic.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp
You can add a custom Connector in Claude Web:
@trieloff, just reopened this issue. I see custom connectors is now supported on Claude Web, but the built-in GitHub Connector isn't working due to lack of DCR support. I understand this is frustrating.
The remote GitHub MCP server doesn't support dynamic client registration yet - each host app needs to manually register an OAuth or GitHub App today. We're working with the Anthropic steering committee to simplify the DCR spec first, as the current implementation is complex (hence why few MCP servers support it). Once there's a more streamlined version, we expect broader adoption - including from us.
In the meantime, our partner team's is looking into interim solutions with Anthropic around registering an app to support the OAuth flow for the remote server.
If we could keep this issue focused on Claude (Web), and use a separate issue for Claude Code and Claude Desktop that will help us triage, as each host app is being turned on individually until DCR is resolved.
- Claude Desktop issue: https://github.com/github/github-mcp-server/issues/799
@D1M1TR10S thank you for reopening the issue. I apologize for not being sufficiently clear in my issue description and would like some feedback on how I could improve the "steps to reproduce" part of the issue to file better bug reports in the future.
Currently, unlike Team & Enterprise plans, trying with the Pro or Max plan gives:
✗ Custom OAuth Client IDs are currently only available for Claude for Work
✗ Failed to add connector
When using Remote MCP URL https://api.githubcopilot.com/mcp/ with Github OAuth credentials in Claude Web; Though, won't solve the DCR issue.
Hey @D1M1TR10S, are there any updates on this? It would be great to be able to use remote Github MCP in Claude Code 🙏🏻
I’ve given up on this issue being resolved. Claude Code can use the GitHub CLI: https://cli.github.com/.
I discovered when the MCP broke and it just carried on working because I had the CLI installed so I've been using the CLI ever since and not bothered with the MCP (I think... there is a broader lesson here about MCPs)
The only thing the GH CLI is really lacking is the CLI "doesn't" support sub issues (!) so I installed this extension: https://github.com/yahsan2/gh-sub-issue
I’m the author of mcp-trino and slack-mcp-client. To better support the MCP adoption in the community and my current company, I’ve implemented the oauth-mcp-proxy, which serves as a simple plug-and-play solution for any Golang-based MCP server to gain OAuth support. This library is actively being used in claude.ai, claude desktop, claude code, ChatGPT, and Perplexity. If anyone is interested, I can take stab to integrate this library into github-mcp-server.
