---
title: "AWS: MCP vendor profile | Agent MCP Directory"
description: "AWS: host or runtime. Products: AgentCore Runtime, plus 2 more. 9 dated facts, prices, standards and two checks, each sourced, read 5 November 2026."
canonical: https://agentmcpdirectory.com/vendors/aws-agentcore
site: "Agent MCP Directory"
last_updated: 2026-11-05
section: "Vendors"
---

# AWS: MCP vendor profile | Agent MCP Directory

> AWS: host or runtime. Products: AgentCore Runtime, plus 2 more. 9 dated facts, prices, standards and two checks, each sourced, read 5 November 2026.

Source: https://agentmcpdirectory.com/vendors/aws-agentcore
Site: Agent MCP Directory
Last reviewed: 2026-11-05

# AWS: MCP vendor profile

Amazon Bedrock AgentCore runs MCP servers as containers in AgentCore Runtime and offers AgentCore Gateway, a managed entry point that turns APIs and Lambda functions into tools for agents, priced per call, as documented by the vendor. AgentCore Runtime adds an Mcp-Session-Id header to any MCP request that lacks one, so clients keep continuity with the same runtime session (docs.aws.amazon.com).

## At a glance

| Listed as | AWS (Amazon Bedrock AgentCore) |
| --- | --- |
| Type | Hosts and runtimes |
| Also covers | gateway or proxy, auth provider |
| Operator | Amazon Web Services |
| Home | aws.amazon.com |
| Price | per vCPU-hour and GB-hour; per 1,000 invocations |
| Read | 5 November 2026 |

## What it does for this layer

AgentCore Runtime expects an MCP server container to listen at 0.0.0.0:8000/mcp, which AWS calls the default path of most official MCP server SDKs ([docs.aws.amazon.com](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-mcp.html)). AgentCore Runtime supports stateless and stateful streamable-HTTP MCP servers; stateless mode (stateless\_http=True) is recommended for basic servers, and stateful mode keeps session state for elicitation, sampling and progress notifications ([docs.aws.amazon.com](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-mcp.html)). AgentCore Gateway includes semantic search so agents can find tools by task context as the tool collection grows ([docs.aws.amazon.com](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway.html)).

AgentCore Gateway pricing is 0.005 USD per 1,000 API invocations such as ListTools, InvokeTool and Ping, 0.025 USD per 1,000 search calls, and 0.02 USD per 100 tools indexed a month ([aws.amazon.com](https://aws.amazon.com/bedrock/agentcore/pricing/)). AgentCore Identity carries no extra charge when used through AgentCore Runtime or AgentCore Gateway ([aws.amazon.com](https://aws.amazon.com/bedrock/agentcore/pricing/)). AgentCore Runtime v1 bills 0.0895 USD per vCPU-hour and 0.00945 USD per GB-hour of memory ([aws.amazon.com](https://aws.amazon.com/bedrock/agentcore/pricing/)).

AgentCore Gateway can apply Policy checks to each tool call, billed per authorization request ([aws.amazon.com](https://aws.amazon.com/bedrock/agentcore/pricing/)). AWS describes AgentCore Gateway as "a fully managed AI gateway" that gives agents a single entry point to tools, other agents and LLMs, not only an MCP tool gateway ([docs.aws.amazon.com](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway.html)).

## Products and plans

| Product | What it does | Price |
| --- | --- | --- |
| AgentCore Runtime | Serverless runtime for agents and MCP servers in containers. | per vCPU-hour and GB-hour; from 0.09 USD; v1 CPU per vCPU-hour (source, as of 5 November 2026) |
| AgentCore Gateway | Managed gateway that exposes APIs, Lambda functions, agents and models as tools. | per 1,000 invocations; from 0.005 USD (source, as of 5 November 2026) |
| AgentCore Identity | Agent identity and credential access for AWS and third-party services. | price not read |

## Standards

| Standard | Part of it | Status | What the page says | Source |
| --- | --- | --- | --- | --- |
| MCP | streamable HTTP | Supports | Runtime runs stateless and stateful streamable-HTTP MCP servers. | docs.aws.amazon.com |

## Checks on its own domain

| Check | Domain | Result | Scanned | Method |
| --- | --- | --- | --- | --- |
| Ora cached score | aws.amazon.com | 60 of 100, grade C | 30 October 2026 | how it was taken |
| Cloudflare agent-readiness scan | aws.amazon.com | 20 of 100, L1 Basic Web Presence; 3 of 15 counted checks passed | 5 November 2026 | how it was taken |

## What it does not do

-   AgentCore is not a public registry of third-party MCP servers.

## Related on this site

Type

-   [Hosts and runtimes](https://agentmcpdirectory.com/vendors/by-type/host/)
-   [Gateways and proxies](https://agentmcpdirectory.com/vendors/by-type/gateway/)
-   [Auth providers](https://agentmcpdirectory.com/vendors/by-type/auth-provider/)

Standards

-   [MCP](https://agentmcpdirectory.com/standards/mcp/)

Section

-   [All vendors](https://agentmcpdirectory.com/vendors/)

Edition

4 November 2026

Method

[How rows are verified](https://agentmcpdirectory.com/method/)

Data

[CSV and JSON](https://agentmcpdirectory.com/data/)

Markdown

[This page as markdown](https://agentmcpdirectory.com/vendors/aws-agentcore/index.md)

## Sources

-   [AWS home](https://aws.amazon.com/bedrock/agentcore/), read 5 November 2026
-   [Deploy MCP servers in AgentCore Runtime - AWS docs](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-mcp.html), read 5 November 2026
-   [Amazon Bedrock AgentCore Gateway - AWS docs](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway.html), read 5 November 2026
-   [Amazon Bedrock AgentCore Pricing - AWS](https://aws.amazon.com/bedrock/agentcore/pricing/), read 5 November 2026

Last reviewed 5 November 2026
