What changed
AWS added an External Tool block to Amazon Connect Customer flows that invokes Model Context Protocol (MCP) tools. Flows connect to third-party applications through Amazon Bedrock AgentCore Gateway and can reuse the same tools configured for agentic experiences to retrieve data or trigger actions, without custom Lambda functions. AWS gives examples such as retrieving CRM case history or banking transaction details during a contact.
Vendor documentation (opens in a new tab)Why it matters
Until now, deterministic flows and AI agents often needed separate integration code for the same back-end systems. A shared MCP tool layer reduces that duplication, but it also means one gateway configuration can affect both scripted and AI-driven experiences, so ownership, change control and permissions for those tools matter more.
CxCave practical context
Who should care
- CX architects
- Developers
- Integration developers
Implementation considerations
REVIEWInventory Lambda-based lookups that duplicate tools already exposed through AgentCore Gateway, pilot the External Tool block on a read-only lookup first, and define who owns and approves changes to shared MCP tools.
CxCave recommendation, not a vendor mandate unless explicitly stated.