Amazon Bedrock AgentCore Gateway Just Became the Enterprise MCP Infrastructure Layer. Here's What Actually Changed.

MCP servers are proliferating fast inside enterprises. Every team ships one, each one independently handles credentials, every security team reviews them separately, and nobody has a unified view of what tools are being called by whom. sits between MCP clients and every MCP server in your organization, acting as the single authenticated entry point for all MCP traffic. Teams build only the business logic for their server. The gateway handles everything else — credential management, policy enforcement, observability, private network routing via and token exchange through capability lets you inject custom authorization logic, sanitization, or request transformation at the gateway layer rather than duplicating it across every server. . Streaming is configured at the CreateGateway / UpdateGateway API level. Session management and elicitation each require explicit enablement — elicitation requires both streaming and sessions to be on. Dynamic listing is specified per target during CreateGatewayTarget. OAuth OBO token exchange is handled through . AgentCore Policy integration remains in preview.

The MCP ecosystem now has a managed enterprise infrastructure layer. The question isn't whether enterprises need something like this — it's whether AWS has built the one they'll actually adopt.

Follow for more coverage on MCP, agentic AI, and AI infrastructure.