The AWS MCP Server is now generally available
AI coding agents can now securely access and manage your AWS infrastructure through a production-ready, cost-free integration layer.
View original announcement →Visual Summary
What's New
AWS has announced the general availability of the AWS MCP Server, a managed server that enables AI coding agents to interact with AWS services securely through the Model Context Protocol (MCP). It is a core component of the Agent Toolkit for AWS, first previewed at re:Invent 2025, and is now production-ready with several new capabilities added since preview. The service is offered at no additional charge, with customers paying only for the underlying AWS resources their agents consume.
How It Works
- The AWS MCP Server exposes AWS service interactions to AI coding agents via the Model Context Protocol, acting as a standardized interface layer between the agent and AWS APIs.
- A single unified tool allows agents to invoke any AWS API, including those requiring file uploads or long-running asynchronous operations.
- Sandboxed Python script execution enables agents to perform multi-step operations against AWS services in an isolated environment that has no access to the local filesystem or shell, reducing the blast radius of unintended actions.
- Agent Skills provide on-demand, curated procedural guidance that agents can discover and load dynamically, keeping context window consumption low while still delivering tested workflows for complex tasks.
- The entire interaction surface is governed by IAM-based access controls, with operational visibility provided through Amazon CloudWatch metrics and AWS CloudTrail audit logging.
Why It's Important
- As AI coding agents become increasingly embedded in developer workflows, giving them safe, auditable access to cloud infrastructure is a critical enterprise requirement.
- The AWS MCP Server addresses this by providing a structured, policy-enforced pathway for agents to act on AWS—eliminating the need for ad-hoc, uncontrolled API access patterns that are difficult to audit or restrict.
- The combination of IAM guardrails, CloudTrail logging, and sandboxed execution means organizations can adopt agentic automation without sacrificing the compliance and security posture they maintain for human operators.
- The removal of credential requirements for documentation search and skill discovery also significantly lowers the onboarding friction for new users and teams evaluating the toolkit.
How It's Different
- Prior to this release, coding agents interacting with AWS typically relied on direct SDK calls, custom tool wrappers, or loosely defined agent SOPs (Standard Operating Procedures), none of which provided a standardized, managed interface with built-in observability.
- The preview version introduced the MCP-based approach but lacked the breadth of API coverage, sandboxed execution, and the more flexible Agent Skills format now available at GA.
- Agent Skills replace the earlier SOP construct with a more dynamic, demand-driven model that avoids bloating the agent's context window with pre-loaded instructions.
- Compared to generic MCP server implementations or self-hosted alternatives, the AWS MCP Server is fully managed, natively integrated with AWS identity and observability services, and purpose-built for AWS API interactions.
When to Prefer It
- The AWS MCP Server is the preferred choice when deploying AI coding agents that need to provision, query, or manage AWS resources as part of automated development or operational workflows.
- It is particularly well-suited for enterprise environments where auditability, least-privilege access, and compliance logging are non-negotiable requirements.
- Teams building agentic pipelines with tools like Amazon Q Developer, Claude, or other MCP-compatible agents that need to perform complex, multi-step AWS operations—such as deploying infrastructure, querying service state, or processing data—will benefit most.
- Organizations that want to avoid the operational overhead of self-hosting and securing their own MCP server infrastructure should also prefer this managed offering.
Availability
- The AWS MCP Server is generally available as of May 6, 2026.
- It is currently supported in two AWS Regions: US East (N.
- Virginia) and Europe (Frankfurt).
- The service itself carries no additional charge; costs are incurred only from the AWS services and resources that agents interact with during execution.
- Regional availability is limited at GA, so workloads with data residency requirements outside these two regions should account for this constraint when planning adoption.