AIToday
Large Language ModelsAmazon AI BlogPublished: Sep 1, 2026, 10:00 JST

Connect an AgentCore Runtime hosted MCP server to Amazon Quick

Connect an AgentCore Runtime hosted MCP server to Amazon Quick

3 Key Points

  1. What happened

    AWS published a guide explaining how to deploy and host an MCP server on AgentCore Runtime, then connect it to Amazon Quick using AgentCore Gateway. The integration lets AI agents in Amazon Quick access external tools and data through the MCP server.

  2. Why it matters

    Amazon Quick users can now reuse common tools and agents exposed through an MCP server instead of building custom connectors for every use case. This promotes reusability and avoids duplication of AI tools, so customers get a way to use your product inside Amazon Quick without custom integrations.

  3. What to watch

    You can use the integration if you have your own REST API, an AWS Lambda function, or a fully managed serverless MCP server hosted on AgentCore Runtime. The guide includes step-by-step instructions, prerequisites like an AWS account and Python 3.10+, and a sample MCP server code.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

This guide is part of AWS's effort to standardize how AI agents connect to external tools and data through the Model Context Protocol (MCP). By providing a path to host an MCP server on AgentCore Runtime and integrate it with Amazon Quick, AWS enables developers to expose tools once and reuse them across multiple chat agents and workflows. The architecture uses AgentCore Gateway as a secure bridge, with inbound authentication handled by Amazon Cognito and outbound authentication via OAuth 2.0 through AgentCore Identity.

The guide offers multiple integration options depending on the user's needs: direct REST API integration via Amazon Bedrock AgentCore Gateway, a serverless Lambda-based approach, or a fully managed serverless MCP server with features like session isolation, extended execution time, and built-in authentication. This flexibility suggests AWS is positioning AgentCore as a central hub for agentic AI workflows, where tools and sub-agents can be shared across applications.

For businesses, the practical implication is reduced development overhead: instead of building custom connectors for every product integration, an MCP server can be deployed once and connected to Amazon Quick, allowing customers to use the product's capabilities inside their existing chat agents and flows. However, the implementation requires technical expertise in AWS services, Python, and MCP, as outlined in the prerequisites and detailed steps.

FAQ
What are the prerequisites for this tutorial?
You need an AWS account, Amazon Quick with an Author or higher subscription, permissions to create IAM roles and policies, and basic AWS knowledge. For the AgentCore setup, you need access to a command-line environment with AWS SDK and Python, plus Amazon Bedrock with Anthropic models enabled. To run the tutorial, you need Python 3.10+, AWS credentials, the AgentCore SDK, the MCP library, and a running Docker daemon.
What is the default path for MCP server containers in AgentCore Runtime?
AgentCore Runtime expects MCP server containers to be available at the path 0.0.0.0:8000/mcp, which is the default path supported by most official MCP server SDKs.
Amazon AI BlogRead Original Article

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleGoldman Sachs: AI capex imbalance to last until 2028