Conversation
…lity Supabase's OAuth token endpoint returns HTTP 201 Created instead of the standard 200 OK. The mcp-go library only accepts 200, causing token exchange to fail even though the response contains a valid access token. Extend OAuthTransportWrapper to normalize 201→200 for token responses, and always create the wrapper for all OAuth servers (not just when extra params are configured). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Deploying mcpproxy-docs with
|
| Latest commit: |
3d0864e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://63d298c4.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://fix-oauth-token-201-status-n.mcpproxy-docs.pages.dev |
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 22626180544 --repo smart-mcp-proxy/mcpproxy-go
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
v0.43.1) only accepts 200 inProcessAuthorizationResponse, causing token exchange to fail despite the response containing a valid access tokenOAuthTransportWrapper.RoundTrip()to normalize 201→200 for token responsesTest plan
🤖 Generated with Claude Code