Inteligencia Artificial

AWS MCP Server Now Available: AI Agents with Secure Access to AWS

The new managed MCP server allows AI assistants to interact with over 15,000 AWS APIs using standard IAM policies and real-time updated documentation.

June 14, 2026 · 3 min read

a blue and white logo

TL;DR: AWS has launched the AWS MCP Server in general availability, a managed MCP server that gives AI agents secure, authenticated access to all AWS services. It includes tools like call_aws, search_documentation, and run_script in a sandbox, plus Skills curated by AWS to reduce hallucinations and improve efficiency.

What Happened?

AWS has announced the general availability of the AWS MCP Server, a managed remote server that implements the Model Context Protocol (MCP). This server allows AI agents and coding assistants to securely and authentically access all AWS services using the user's existing IAM credentials. The server is part of the Agent Toolkit for AWS and offers a fixed, small set of tools that do not consume model context. According to the AWS News Blog, the server solves a recurring problem: how to give an agent real, authenticated access to AWS without handing over the keys to the kingdom. The answer is a managed MCP server that acts as an intermediary, applying the user's IAM policies and limiting actions to a predefined set of tools.

Why Is It Important?

Until now, AI agents struggled to work deeply with AWS. Without access to updated documentation, they relied on outdated training data and often generated overly permissive IAM policies or infrastructure not ready for production. The AWS MCP Server solves this by providing tools like call_aws (executes any AWS API), search_documentation and read_documentation (retrieve updated documentation), and run_script (executes Python scripts in an isolated environment with no network access). Additionally, it introduces Skills (guides curated by AWS teams) that replace the previous Agent SOPs, reducing errors and token consumption. The AWS blog highlights that agents used to resort to the AWS CLI instead of CDK or CloudFormation, producing infrastructure that works in a demo but is not production-ready. With the MCP Server, the agent can use call_aws to directly invoke service APIs, following best practices embedded in the Skills.

What Impact Will It Have?

This release marks a milestone in the integration of AI with cloud infrastructure. Developers can now delegate complex provisioning and management tasks to agents with confidence that they will follow best practices and security policies. The ability to run scripts in a sandbox without network access allows data processing without exposing the local system. Additionally, reduced tokens per interaction and support for IAM context keys simplify enterprise adoption. It is expected to accelerate the creation of more autonomous and secure coding assistants in AWS environments. Compared to previous releases like Amazon Bedrock Agents, the MCP Server eliminates the need to manage agent infrastructure, offering a standard integration point. For businesses, this means lower risk of insecure configurations and faster development of cloud-native applications. End users will benefit from more competent assistants that can execute tasks like creating S3 buckets, launching EC2 instances, or deploying serverless applications with a single natural language instruction.

What Should Readers Know?

  • Availability: The AWS MCP Server is now generally available. It does not require separate IAM permissions to use the server; it integrates with standard IAM policies via context keys. According to the blog, new APIs are supported within days of their release.
  • Key Tools: call_aws (15,000+ APIs), search_documentation, read_documentation (no authentication required), and run_script (sandbox without network). The fixed set of tools prevents the agent from consuming model tokens to choose which tool to use, improving efficiency.
  • Skills vs SOPs: Skills are guides maintained by AWS service teams that replace Agent SOPs, offering validated best practices and reducing hallucinations. Being curated by the service teams themselves, they ensure the agent follows recommended procedures.
  • Security: The server uses the user's IAM credentials. Scripts run in a sandbox with no network access, limiting risks. Additionally, context keys allow restricting which tools the agent can use, adding a layer of control.
  • Efficiency: Fewer tokens per interaction, reducing costs and improving speed in complex workflows. By not consuming model context with tools, the agent can dedicate more tokens to the actual task.
"The AWS MCP Server allows AI agents to access AWS securely and authentically, without exposing credentials or granting excessive permissions." — AWS News Blog

In summary, the AWS MCP Server represents a significant advance in the interaction between AI and cloud services. By providing controlled, documented, and efficient access, it paves the way for a new generation of coding assistants that can operate autonomously and securely in production environments. Developers and businesses that adopt this tool will be able to accelerate their development cycles while maintaining strict security control.

Keep reading