Bedrock AgentCore adds stateful MCP for interactive agent workflows
Amazon Bedrock AgentCore Runtime now supports stateful Model Context Protocol (MCP) client capabilities, enabling AI agents to pause execution for user input, request LLM-generated content, and stream real-time progress updates. Previously, stateless MCP implementations could only execute one-way tool calls without bidirectional communication. The update introduces three new capabilities: elicitation for mid-execution user requests, sampling for dynamic LLM content generation, and progress notification for long-running tasks. Stateful mode provisions dedicated microVMs per user session with up to 8 hours persistence, maintaining conversation continuity through session identifiers.
TL;DR
- →Bedrock AgentCore Runtime adds stateful MCP support, enabling interactive multi-turn agent workflows that can pause for user input or LLM sampling
- →Three new client capabilities: elicitation (request user input), sampling (request LLM content), and progress notification (stream real-time updates)
- →Stateful mode provisions isolated microVMs per session lasting up to 8 hours, replacing stateless HTTP model that couldn't maintain conversation context
- →Completes bidirectional MCP protocol implementation, allowing servers to initiate requests back to clients rather than only responding to tool calls
Why it matters
Stateful MCP support removes a fundamental constraint in agent design: the inability to maintain conversation threads or request clarification mid-execution. This capability gap has forced developers to work around limitations in long-running workflows, interactive debugging, and real-time feedback loops. The addition brings MCP implementations closer to practical agent requirements where workflows often need human-in-the-loop validation or dynamic content generation during execution.
Business relevance
For operators building production agents, stateful MCP unlocks use cases that require interactive workflows, such as approval gates, clarification requests, or progress reporting during extended operations. This reduces the need for custom workarounds and external orchestration layers, lowering development complexity and time-to-market for agent applications. The 8-hour session persistence and isolated microVMs provide a managed alternative to self-hosted MCP infrastructure.
Key implications
- →Developers can now build agents that pause mid-execution for user input or LLM sampling, enabling interactive workflows previously impossible with stateless implementations
- →Session-based architecture with dedicated microVMs per user creates isolation and state persistence, but introduces operational considerations around resource allocation and session lifecycle management
- →Bidirectional MCP protocol support positions Bedrock as a more complete MCP runtime, potentially increasing adoption among developers already invested in the open standard
- →The 8-hour session limit and 15-minute idle timeout create practical constraints for long-running or intermittent workflows that may require external session management
What to watch
Monitor adoption patterns to see which use cases drive stateful MCP demand and whether the session timeout windows prove sufficient for real-world workflows. Watch for competing implementations from other cloud providers or open-source projects that may offer different session persistence models. Track whether the bidirectional protocol capabilities become table stakes for agent platforms or remain a differentiator.
vff Briefing
Weekly signal. No noise. Built for founders, operators, and AI-curious professionals.
No spam. Unsubscribe any time.
