{"resourceId":"aws-connect-flows-mcp-tools-agentcore-gateway-20261102","versions":[{"version":"external-6b83a7120db03624c5a28e38a69f95cab71819921e7f90f06600a2694b0254ed","resource":{"id":"aws-connect-flows-mcp-tools-agentcore-gateway-20261102","title":"Amazon Connect flows can now call MCP tools through Bedrock AgentCore Gateway via a new External Tool block, but not yet in GovCloud","organization":"Amazon Web Services (Amazon Connect; Bedrock AgentCore)","sector":"Contact centers; citizen services","geography":"Commercial AWS Regions listed (US East N. Virginia, US West Oregon, Canada Central and others); not GovCloud","publishedAt":"2026-11-02","publicationDate":"2026-11-02","eventDate":null,"sourceName":"AWS What's New","sourceLabel":"Amazon Connect Customer now supports Model Context Protocol (MCP) tools in flows","sourceUrl":"https://aws.amazon.com/about-aws/whats-new/2026/10/connect-flows-mcp-tools/","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["developers-agents","data-security","operating-model"],"finding":"AWS announced (feed date Nov 2) that Amazon Connect Customer flows can invoke Model Context Protocol tools through a new External Tool block, connecting to third-party applications via Amazon Bedrock AgentCore Gateway and reusing the same tools used by agentic experiences, without custom Lambda functions. AWS's example is retrieving CRM case history or transaction details during a contact. The feature is listed in nine commercial Regions; GovCloud is not listed.","sledRelevance":"311 centres, benefits call lines and nonemergency lines built on Amazon Connect (the archive includes Richmond's nonemergency deployment) could pull case or account data into flows with less custom code. The absence of GovCloud limits use where CJIS or similar data must stay there.","evidence":"Vendor feature notice; no customer, reliability or security evaluation.","architectureImplications":"Flow-level External Tool block calls MCP tools exposed through AgentCore Gateway, replacing Lambda glue; the same tools can be shared between deterministic flows and AI agents.","governanceImplications":"Shared tools between flows and agents means one change can affect both channels; agencies need a tool inventory and change control.","securityPrivacyImplications":"Each MCP tool becomes a path from a public-facing contact into back-office systems; gateway authorization, least-privilege scopes and logging need review. The archive includes AgentCore security findings (Zenity AgentCorruption, Starter Toolkit bulletin) that make this review necessary.","caveats":"Commercial Regions only per the notice. No reliability, latency or failure-handling detail. Vendor claim.","streamIds":["aws"],"roles":{"sales":"Lead with integration effort, not AI. Agencies running Amazon Connect for 311 or benefits lines often pay for custom Lambda glue to look up case data; this lets flows call shared MCP tools instead. Be clear that it is not in GovCloud, so it fits commercial-Region deployments with appropriate data. A sensible offer is a review of existing flow integrations to see which could move to governed tools, with security sign-off as part of scope.","engineering":"Engineering should map which current Lambda integrations could become MCP tools behind AgentCore Gateway and what each tool can read or change. Check the Region list against where the instance runs, and confirm timeout, error and fallback behaviour inside a flow when a tool fails. Review gateway authentication, tool scopes and logs, given archived AgentCore security findings. Because flows and agents would share tools, design versioning so a tool change does not silently break a live flow.","delivery":"Delivery should pilot one low-risk lookup, such as case status, before touching anything that writes data. Build a tool inventory with owners and versions, set change control that covers both flows and agents, and test failure paths with real call scenarios. Measure handle time and error rates before and after. Keep the Lambda path available for rollback until the tool path has run cleanly for an agreed period."},"roleDetails":{"sales":{"customerProblem":"Contact centres need case and account data in call flows without maintaining custom integration code for each system.","stakeholders":["Contact centre director","311 or benefits program manager","Integration lead","CISO"],"discoveryQuestions":["Which Connect flows use custom Lambda lookups today?","Does your Connect instance run in a listed commercial Region?","Which back-office systems would tools reach, and with what data classification?"],"valueHypothesis":"Shared MCP tools may cut integration maintenance for Connect flows; no measured benefit is reported.","potentialEngagement":"An integration and security review of existing Connect flows, ending in a short list of tool candidates.","unsupportedClaims":["Availability in GovCloud","Reduced handle time","Security of third-party tools"]},"engineering":{"fit":"Commercial-Region Amazon Connect deployments with data lookups; not GovCloud.","architectureIntegration":"Connect flow External Tool block to MCP tools via Bedrock AgentCore Gateway, replacing Lambda functions.","prerequisites":["Connect instance in a supported Region","AgentCore Gateway configured","Tool inventory and owners"],"constraints":["Nine commercial Regions only","No published failure-handling detail","Tools shared with agents"],"security":"Least-privilege tool scopes, gateway authentication, logging of every invocation, and review against known AgentCore findings.","proofOfValue":["Test tool failure and timeout paths in a flow","Verify tool scopes prevent unintended writes","Compare handle time on one flow before and after"]},"delivery":{"work":"Pilot one read-only lookup tool in a single flow with rollback to Lambda.","dependencies":["AgentCore Gateway setup","Back-office system APIs","Security review"],"ownership":"Contact centre platform owner owns flows; integration lead owns the tool catalogue.","skillsAdoption":"Flow designers need training on the External Tool block and tool versioning.","governanceCheckpoints":["Security review before production","Post-pilot review of errors","Change-control check for shared tools"],"acceptanceCriteria":["Proposed: tool lookups succeed in an agreed share of pilot contacts","Proposed: no unauthorized write actions in testing"],"risks":["Tool change breaks live flows","Over-scoped tools expose back-office data","Region limits block regulated workloads"]}},"retrievedAt":"2026-11-03T04:02:03Z","enrichedAt":"2026-11-03T04:05:18Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Could reduce agent handle time if data retrieval works; no measured effect reported.","procurementImplications":"Lower custom-code effort may shift integrator scope from Lambda development to tool governance.","operatingModelImplications":"Moves integration ownership toward whoever governs the AgentCore Gateway tool catalogue.","sourceVerification":{"openedUrl":"https://aws.amazon.com/about-aws/whats-new/2026/10/connect-flows-mcp-tools/","referenceExcerpt":"you can connect flows to third-party applications through Amazon Bedrock AgentCore Gateway and reuse the same tools used by your agentic experiences","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}