AWS puts MCP Apps widgets inside Bedrock AgentCore

AWS built a runtime for MCP Apps, the extension that lets an MCP server hand back a rendered HTML widget instead of plain text. Bedrock AgentCore Runtime hosts the server in an isolated session per user. AgentCore Gateway puts one endpoint in front of it that any MCP Apps-compatible host can call, per AWS's walkthrough.

The stakes are about where the interactive layer of an agent lives. Until now, MCP Apps was a spec you could implement yourself, with no managed host built for it.

AWS's sample app, Unicorn Rentals, is backed by Lambda functions and a DynamoDB table. It renders the same widget inside ChatGPT or Claude without any client-specific code, because MCP Apps was built host-agnostic from the start.

A team building an internal tool, a booking flow, a dashboard, doesn't have to pick a chat client and build for it. One MCP server, fronted by one Gateway endpoint, works across whichever assistant the end user opens. AWS's post calls the sessions isolated but doesn't say how that isolation is enforced. It also doesn't compare cold-start latency against a plain text-only MCP server.

What to watch

Watch whether Google or Microsoft put out a comparable managed host for MCP Apps servers in the next few months. If they do, the extension stops being an AWS feature and becomes a category every cloud supports. If they don't, AWS just built a moat around a spec nobody else productized.