DOCS-1788 - Document AgentCore Gateway setup for MCP server - #6980
Open
kimsauce wants to merge 2 commits into
Open
DOCS-1788 - Document AgentCore Gateway setup for MCP server#6980kimsauce wants to merge 2 commits into
kimsauce wants to merge 2 commits into
Conversation
Customers connecting the MCP server through an AWS Bedrock AgentCore Gateway (to aggregate multiple MCP servers behind one endpoint) hit an opaque "Error parsing ClientCredentials response" error because the gateway target's OAuth2 credential provider config needs grantType: CLIENT_CREDENTIALS explicitly set. Add a Manual OAuth setup subsection with the AWS CLI commands and that gotcha called out. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Per PR review feedback: a full AWS CLI walkthrough for one gateway client (of ~10 supported clients this doc otherwise treats generically) is a maintenance liability since gateway configs can change faster than docs get updated, and the previous placement nested it under "Configure in Claude Code CLI" even though it's unrelated to that client. Replace with a two-sentence note under the generic MCP-compatible client section, keeping only the Sumo-specific fact that actually caused the reported error: grantType: CLIENT_CREDENTIALS must be set explicitly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
kdwink
approved these changes
Aug 3, 2026
kdwink
left a comment
kdwink
left a comment
Collaborator
There was a problem hiding this comment.
This small additional note looks good to me.
We could potentially remove this last part of the last sentenc:
"though Sumo Logic's own OAuth setup doesn't need it named explicitly"
In our setup user do select the client type as "client credentials" and behind the scenes that configures a CLIENT_CREDENTIALS grant type. So while true, in a sense, maybe not relevant? Not a big deal either way.
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.
Purpose of this pull request
Customers connecting the Sumo Logic MCP server through an AWS Bedrock AgentCore Gateway (to aggregate multiple MCP servers behind one endpoint) hit an opaque
Error parsing ClientCredentials responseerror, because the gateway target's OAuth2 credential provider config needsgrantType: CLIENT_CREDENTIALSexplicitly set — an AWS requirement not obvious from our own OAuth setup docs.Adds a new "Connect through an AWS Bedrock AgentCore Gateway" subsection under Manual OAuth setup in
docs/api/mcp-server.md, covering:grantTypefield, and the exact error it causes if omitted.oauth.md) can be used instead of specifyingtokenEndpointdirectly.Source: internal Slack thread (INFOR customer, $3.2M ARR); fix confirmed working by Lokent Banswani; requested by Vijit Singhal.
Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-1788