Skip to content

DOCS-1788 - Document AgentCore Gateway setup for MCP server - #6980

Merged
kimsauce merged 4 commits into
mainfrom
DOCS-1788-agentcore-gateway-mcp-doc
Aug 4, 2026
Merged

DOCS-1788 - Document AgentCore Gateway setup for MCP server#6980
kimsauce merged 4 commits into
mainfrom
DOCS-1788-agentcore-gateway-mcp-doc

Conversation

@kimsauce

@kimsauce kimsauce commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

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 response error, because the gateway target's OAuth2 credential provider config needs grantType: CLIENT_CREDENTIALS explicitly set — an AWS requirement not obvious from our own OAuth setup docs.

Adds one sentence to the OAuth section of docs/api/mcp-server.md noting 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 need grantType: CLIENT_CREDENTIALS set 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

  • Minor Changes - Typos, formatting, slight revisions
  • Update Content - Revisions, updating sections
  • New Content - New features, sections, pages, tutorials
  • Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

https://sumologic.atlassian.net/browse/DOCS-1788

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>
@kimsauce
kimsauce requested a review from JV0812 as a code owner August 3, 2026 15:37
@kimsauce kimsauce self-assigned this Aug 3, 2026
@cla-bot cla-bot Bot added the cla-signed Contributor approved, listed in .clabot file label Aug 3, 2026
@kimsauce
kimsauce requested review from ganano and kdwink August 3, 2026 15:41
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 kdwink left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

kimsauce and others added 2 commits August 4, 2026 10:56
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>
@kimsauce
kimsauce enabled auto-merge August 4, 2026 17:57
@kimsauce

kimsauce commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator Author

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.

Thanks, @kdwink ! Just applied this change.

@kimsauce
kimsauce added this pull request to the merge queue Aug 4, 2026
Merged via the queue into main with commit 87ae7bf Aug 4, 2026
4 checks passed
@kimsauce
kimsauce deleted the DOCS-1788-agentcore-gateway-mcp-doc branch August 4, 2026 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed Contributor approved, listed in .clabot file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants