Amazon Bedrock AgentCore Runtime
AWS's managed **stateful agent runtime** for the Bedrock platform, providing isolated **microVMs** (Firecracker-style lightweight VMs) per agent session that preserve stateful MCP-server features — elicitation, sampling, progress notifications — across the otherwise stateless transport layer of MCP 2026-07-28. AgentCore Runtime lets developers deploy MCP servers as managed AWS workloads without operating their own session-affinity-aware load balancers.
Definition
AWS's managed **stateful agent runtime** for the Bedrock platform, providing isolated **microVMs** (Firecracker-style lightweight VMs) per agent session that preserve stateful MCP-server features — elicitation, sampling, progress notifications — across the otherwise stateless transport layer of MCP 2026-07-28. AgentCore Runtime lets developers deploy MCP servers as managed AWS workloads without operating their own session-affinity-aware load balancers.
The MCP 2026-07-28 spec made the *protocol* stateless to enable horizontal scaling (no Mcp-Session-Id header, no initialize/initialized handshake), but agents still genuinely need stateful execution context across many tool calls. AgentCore Runtime resolves the layer split by managing statefulness *in the runtime* (isolated microVMs that survive across requests) while keeping the *protocol* stateless (so AWS can route requests freely across the microVM pool without the load balancer needing protocol awareness).
Production deployment of MCP servers on AWS without operating session-aware infrastructure; enterprise agentic workloads requiring AWS-native IAM + VPC + KMS integration; long-running agent sessions that must preserve elicitation/sampling/progress state across hours of execution; mission-critical agents needing the operational SLAs of managed AWS infrastructure.
Recent developments
- AgentCore Runtime added stateful MCP support. AWS announcement positions it as the production-grade way to run MCP servers with stateful features intact. Per AWS — Amazon Bedrock AgentCore Runtime stateful MCP support.
- Layer separation is the architectural innovation. Protocol stays stateless (horizontal-scaling-friendly); runtime is stateful (microVM-isolated). This same pattern is now being copied by Azure + GCP's managed-agent equivalents. Per Model Context Protocol Blog — 2026-07-28 Release Candidate.
- First mover among managed MCP runtimes. Pre-AgentCore Runtime, enterprises self-managed their MCP server fleet on ECS / Fargate / EKS with custom session affinity. AgentCore is the first managed product to abstract that away. Per AWS — Deploying MCP servers on Amazon ECS.
Connections 7
Outbound 5
scoped_to1implements1enables1competes_with1