Skip to main content

OAuth issue incorrect for MCP

  • Sep 20, 2026 6:03 AM UTC
  • 4 replies
  • 279 views

heaths
Forum|alt.badge.img+7

I appreciate that you tested this the Strava MCP with Claude so I imagine it works, but they aren’t the only agent out there. I’m getting an immediate HTTP 403 with Copilot CLI, and when having it introspect why, it reports:

Root cause: it’s not failing because your  strava-mcp  entry is missing or malformed; Copilot is rejecting Strava’s OAuth metadata as invalid.

Your config is a normal remote MCP entry in  ~/.copilot/mcp-config.json :

"strava-mcp": {
  "type": "http",
  "url": "https://mcp.strava.com/mcp"
}

But the Copilot log shows the auth flow dies here:

 OAuth authentication failed for strava-mcp: MCPOAuthError: Incompatible authorization server: authorization server advertised an issuer that does not match the URL its metadata was discovered from (RFC 8414 §3.3); refusing to connect 

What’s happening is:

1.  strava-mcp  challenges the client with an OAuth protected-resource URL on  www.strava.com .
2. That metadata points to  https://www.strava.com/mcp-issuer  as the authorization server.
3. The authorization-server metadata served from that path reports  "issuer":"https://www.strava.com"  instead of the discovered issuer URL/path.
4. Copilot CLI rejects that mismatch on purpose, so authentication never completes.

Bottom line: this is a server-side OAuth metadata bug/incompatibility in Strava’s MCP endpoint, not a bad local Copilot config. The fix has to be on Strava’s side: their protected-resource / authorization-server metadata needs to advertise a consistent issuer.

 

It would be great if the issue followed the OAuth spec so any agent—even ones people wrote themselves (seems to be the thing these days)—could use it.

4 replies

Jan_Mantau
Forum|alt.badge.img+26
  • Hub Powerhouse
  • Sep 20, 2026 6:53 PM UTC

See https://support.strava.com/en-us/articles/15401531-what-is-the-strava-mcp-connector, supporting other AI clients is still under consideration.


Forum|alt.badge.img
  • Hub Starter
  • Oct 13, 2026 8:52 PM UTC

I'm independently reproducing this exact OAuth issuer mismatch on macOS using mcp-remote v0.14.3, installed through Homebrew, while attempting to connect ChatGPT to Strava's official MCP endpoint.

MCP endpoint: https://mcp.strava.com/mcp

OAuth discovery succeeds, but authentication fails with:

IssuerMismatchError: expected "https://www.strava.com/mcp-issuer", received "https://www.strava.com"

I independently confirmed the mismatch by retrieving Strava's public OAuth authorization-server metadata using curl. The returned issuer value is https://www.strava.com, which differs from the issuer URL advertised during MCP discovery.

I understand that Claude is currently the officially supported MCP client and that support for other clients is under consideration.

However, this appears to be a specific OAuth metadata consistency issue under RFC 8414, rather than simply a request for ChatGPT integration.

Could the engineering team confirm whether this issuer mismatch is intentional or a known issue, and whether correcting it is planned?

Resolving the discrepancy would help standards-compliant MCP clients authenticate without weakening OAuth security checks.

Thank you!


Forum|alt.badge.img
  • Hub Starter
  • Oct 29, 2026 6:58 AM UTC

This is actually quite pathetic of Strava, Claude is like the Tinkertoy of AI tools and Gemini is the living embodiment of both dumb and dumber, yet those are the only tools you support.

 

I actually signed up with premium just for the AI access and then they only support these monkey tools


Forum|alt.badge.img
  • Hub Starter
  • Nov 19, 2026 8:54 PM UTC

Hi,

I'm experiencing the same issue while trying to connect Strava's official MCP server (https://mcp.strava.com/mcp) to ChatGPT.

ChatGPT fails with the following error:

"Couldn't discover OAuth settings. Check the server URL and retry, or enter the settings manually."

I've investigated the OAuth endpoints and found that the protected resource metadata advertises:

"authorization_servers": [
"https://www.strava.com/mcp-issuer"
]

However, the OAuth authorization server metadata at:

https://www.strava.com/.well-known/oauth-authorization-server/mcp-issuer

returns:

"issuer": "https://www.strava.com"

These values don't match, which appears to violate OAuth issuer validation requirements.

Additionally, the authorization server metadata doesn't advertise code_challenge_methods_supported, which may cause compatibility issues with ChatGPT's PKCE requirements.

I've also tried manually configuring the authorization, token, and dynamic client registration endpoints in ChatGPT, but the connection still fails.

Is ChatGPT integration something Strava is planning to support? Since Strava already provides an official MCP server for other AI clients, it would be great to make it compatible with ChatGPT as well.

I'd be happy to help test or troubleshoot the integration further