Remote: Incompatibility with Claude (Web) Integrations

[trieloff]

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:

1. even after entering the URL with a trailing slash, Claude corrects it to https://api.githubcopilot.com/mcp
2. 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

1. open https://claude.ai/settings/integrations
2. log in to Claude, if not logged in
3. click "Add integration"
4. enter "Integration name": GitHub
5. enter "Integration URL": https://api.githubcopilot.com/mcp/
6. click "Add"
7. locate the "GitHub" integration in the list of integrations
8. 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.

[kamal]

The error is clearer when you attempt to add it to Claude Code. It complains of Dynamic client registration failing.

[trieloff]

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.

[gfreitash]

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=

[JayDoubleu]

Same here. Claude code doesnt seem to work with remote github mcp server

[minhluuquang]

Same issue here

[JayDoubleu]

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.

[mkaziz-paypal]

Seeing the same issue as well. The native Github integration doesn't expose the MCP server and you cannot manually add the remote MCP.

[mculp]

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.

[isvicy]

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

[tkinz27]

I had the exact same issue in gemini-cli but I thought the issue was on gemini-cli's side. I created this ticket google-gemini/gemini-cli#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.