DOCS-1788 - Document AgentCore Gateway setup for MCP server - #6980
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
left a comment
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.
Removes the comparison to Sumo Logic's own OAuth setup, which the reviewer noted is not clearly relevant since Sumo's client-credentials client type configures the same grant type behind the scenes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Thanks, @kdwink ! Just applied this change. |
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 one sentence to the OAuth section of
docs/api/mcp-server.mdnoting that the MCP server works behind gateway aggregators like AWS Bedrock AgentCore Gateway, that these should be configured with the Client Credentials flow, and that gateways may needgrantType: CLIENT_CREDENTIALSset explicitly to avoid the error above.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