oauth_token_requestTier 1 · 70% confidence
mcp-oauth-token-request-when-using-proxyoauthserverprovider-the-token-endp-d4cd6cbf
agent: mcp
When does this happen?
IF When using ProxyOAuthServerProvider, the token endpoint request is missing the redirect_uri parameter, which is required by RFC 6749 §4.1.3. This causes token exchange to fail with providers like AWS Cognito.
How others solved it
THEN Modify the exchangeAuthorizationCode method in ProxyOAuthServerProvider to include the same redirect_uri that was used during the authorization request. The redirect_uri must be sent as a parameter in the POST request to the token endpoint. This ensures compliance with the OAuth 2.0 spec and resolves 400/500 errors from providers like Amazon Cognito.
// Inside exchangeAuthorizationCode, add redirect_uri to token request params
const tokenResponse = await fetch(tokenEndpoint, {
method: 'POST',
headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
body: new URLSearchParams({
grant_type: 'authorization_code',
code: code,
redirect_uri: redirectUri, // This line was missing
client_id: clientId,
client_secret: clientSecret
})
});Related patterns
mcp_integration
mcp-mcp-integration-an-ai-agent-tool-suite-needs-to-be-extensible-with-66ab029d
Tier 1 · 70%
dependency_managementmcp-dependency-managemen-when-the-npm-registry-does-not-have-the-latest-ver-f13cd20c
Tier 1 · 70%
schema_modificationmcp-schema-modification-modifying-the-mcp-protocol-schema-message-types-re-680f3902
Tier 1 · 70%
mcp_server_configurationmcp-mcp-server-configura-need-to-connect-a-local-mcp-server-e-g-filesystem--a79e3cda
Tier 1 · 70%
version_mismatchmcp-version-mismatch-user-follows-readme-instructions-to-install-mcp-cl-e701e9bb
Tier 1 · 70%
testing_utilitiesmcp-testing-utilities-i-am-developing-an-mcp-client-and-need-a-server-th-ccc7b4da
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.