Amazon Bedrock AgentCore Gateway
Current Spec Verified Confidence: High (0.90)Amazon Bedrock AgentCore Gateway is an MCP server published by Amazon Web Services with verified support for the current MCP specification revision (2026-07-28). It is the first-party server from Amazon Web Services. Last verified 2026-08-07.
Does Amazon Bedrock AgentCore Gateway support the current MCP specification (2026-07-28)?
Yes. Amazon Bedrock AgentCore Gateway has verified support for MCP revision 2026-07-28, the current stable specification (last verified 2026-08-07).
Is Amazon Bedrock AgentCore Gateway a first-party (official) MCP server?
Yes. Amazon Bedrock AgentCore Gateway is the first-party MCP server published by Amazon Web Services (last verified 2026-08-07).
Does Amazon Bedrock AgentCore Gateway support MCP revision 2026-07-28?
Yes. Amazon Bedrock AgentCore Gateway supports MCP revision 2026-07-28 (checked 2026-08-07).
When were Amazon Bedrock AgentCore Gateway's facts last verified?
2026-08-07. Each fact on this page links to the sources used to verify it.
Which MCP concepts apply to Amazon Bedrock AgentCore Gateway?
- Stateless core - The 2026-07-28 revision's redesign of MCP from a bidirectional stateful protocol into a request/response stateless one: the initialize handshake and protocol-level session are removed, every request carries its protocol version, client identity, and capabilities in _meta, and any request can land on any server instance behind a plain load balancer.
Amazon Bedrock AgentCore Gateway is a managed AWS service that fronts
customer-registered tool targets over MCP. It differs from most records
in this catalog in that there is no installable artifact and no single
endpoint: each customer receives a per-tenant gateway address following
the pattern
https://gateway-id.gateway.bedrock-agentcore.<region>.amazonaws.com/mcp,
and the tools it exposes come from targets the customer registers.
Authorization uses OAuth 2.0 client credentials with a bearer token.
AWS published a post on 2026-07-28, by Principal Product Manager Sean
Eichenberger and Software Development Engineer Luca Chang, enumerating
the 2026-07-28 revision features the Gateway
supports: the stateless protocol with per-request _meta parameters,
Mcp-Method and Mcp-Name header routing, server-to-client
communication via Multi Round-Trip Requests using InputRequiredResult
with opaque requestState tokens, reverse-DNS extension governance,
OAuth 2.0 and OpenID Connect alignment, separation of transport failures
from application outcomes, and full JSON Schema 2020-12 support.
Support is opt-in per gateway rather than a property of a shipped
version. A customer enables it by calling
aws bedrock-agentcore-control update-gateway with the revision included
in the supportedVersions protocol configuration. The AWS developer
guide for using a Gateway with MCP names no protocol revision at all, so
the blog post is the only revision evidence. AWS publishes no AgentCore
entry in the official MCP Registry.
Which MCP spec revisions does Amazon Bedrock AgentCore Gateway support?
Amazon Bedrock AgentCore Gateway has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2026-07-28 | Supported | Source |
How widely adopted is Amazon Bedrock AgentCore Gateway?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
How was this verified, and what are the sources?
Verified · method: vendor-announcement
· confidence 0.90 (High).
- AWS Machine Learning blog post dated 2026-07-28 by Sean Eichenberger and Luca Chang - lists the 2026-07-28 features AgentCore Gateway supports including the stateless protocol, Mcp-Method and Mcp-Name header routing, Multi Round-Trip Requests, extensions governance, OAuth and OpenID Connect alignment, transport-versus-application error separation and JSON Schema 2020-12, and gives the UpdateGateway call with supportedVersions of ["2025-11-25", "2026-07-28"] - accessed
- AWS Bedrock AgentCore developer guide "Using a Gateway with MCP" - gives the per-tenant endpoint pattern gateway-id.gateway.bedrock-agentcore.<region>.amazonaws.com/mcp, documents streamable-http and OAuth bearer-token authorization, and names no MCP protocol revision - accessed
- Official MCP Registry searches for agentcore and bedrock - return no AWS-published entry; matches are com.geiant/mcp-agentcore, io.github.nirholas/agentcore-payments-mcp and com.bedrocknews/news - accessed