AWS shows MCP Apps on Amazon Bedrock AgentCore

The post arrives as customers increasingly interact with digital services through AI hosts like ChatGPT and Claude, which creates a need to serve rich UI across those applications without tying the service to any single host. AWS positions MCP Apps, an extension of the Model Context Protocol, and Amazon Bedrock AgentCore as the pairing that meets both needs. The walkthrough uses Unicorn Rentals to show four steps: list available unicorns as cards, book one by name, view active bookings as text, and return the unicorn with the total cost calculated from duration and hourly rate.

Architecturally, the MCP app is a thin protocol adapter that delegates business logic to an AWS Lambda function backed by Amazon DynamoDB. AgentCore runtime hosts the app in a secure, serverless, session-isolated environment with native MCP support, while AgentCore Gateway exposes it through a single managed endpoint. AWS notes the Lambda could represent existing services on Amazon ECS, Amazon EKS, or other compute, which suggests a path for organizations that already run business logic on AWS. The same server is shown connecting to ChatGPT Developer Mode and Claude Connectors, and AWS states it works with other MCP Apps-compatible hosts.

Looking ahead, the approach's value for teams may hinge on how much operational work AgentCore removes, since AWS says runtime handles scaling, session isolation, health monitoring, and infrastructure management. The production cautions around consumption-based pricing, CloudWatch monitoring, and Amazon Bedrock Guardrails are likely where the real trade-offs surface for anyone moving beyond the sample.