Connect an AgentCore Runtime hosted MCP server to Amazon Quick
Amazon Web Services Vivek Ghatala
AWS shows how to hook an AgentCore Runtime MCP server into Amazon Quick. It lets Quick use outside tools safely, instead of rebuilding connectors for each one.
Based on reporting by Amazon Web Services, Vivek Ghatala — read the original for the full story.
Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error
AWS is pushing a cleaner way to wire tools into Amazon Quick: host the MCP server on AgentCore Runtime, put AgentCore Gateway in front of it, and let Quick talk to that setup with authentication on both sides. The pitch is straightforward. If you already have an MCP server, connect it. If you don’t, AWS says you can deploy one on its own guidance and keep the whole thing inside the AWS stack.
The reason this matters is reuse. Once a tool lives behind an MCP server, clients can call it from Quick chat agents and Flows without someone rewriting the same connector over and over. AWS also frames this as a way to cut duplication for AI tools and sub-agents, which is the kind of work that usually turns into a maintenance tax later.
The setup AWS describes splits the security story into two pieces. Inbound Auth covers requests from Amazon Quick to AgentCore Gateway, with Amazon Cognito used in the example. Outbound Auth covers the Gateway’s calls to AgentCore Runtime, and AWS uses AgentCore Identity plus OAuth 2.0 because the MCP protocol requires it. The Gateway and Runtime both sit inside Amazon Bedrock AgentCore, the managed service AWS is using for the whole flow.
The tutorial walks through a sample server, then deployment with the Bedrock starter kit. The sample code uses FastMCP with stateless_http=True, which AWS says is required for AgentCore Runtime compatibility. From there, the steps move through IAM, two Cognito user pools, an OAuth client in AgentCore Identity, and then the Gateway itself. Only after that do you register the MCP integration in Amazon Quick and point it at the Gateway endpoint.
There’s also a second path for simpler setups. If you only need a bare-bones serverless agent, AWS says you can use Lambda. If you already have a REST API or one on Amazon API Gateway, you can connect that directly through AgentCore Gateway. But the headline here is the fully managed MCP route: session isolation, extended execution time, persistent file systems, built-in authentication, observability, enhanced payload, bidirectional streaming, and evaluations, all packaged up for Quick.
My take — AI-written commentary, not fact-checked reporting
This is AWS doing what AWS does best: turning a messy integration problem into a long checklist of branded services. That’s not a compliment or an insult, just the cloud business model in a suit. The useful part is that MCP is becoming the common tongue for tools; the annoying part is that you still need a map, a token, and probably a coffee before anything talks to anything else.
Read more about this at: Amazon Web Services