AWS MCP: Documentation
Updated:
Connection
The AWS MCP Server's managed HTTP endpoint (preview 2026) runs inside your own AWS account — the exact address is issued when you activate the service in the console, with IAM authentication and SigV4 request signing. For local use there are stdio servers from the github.com/awslabs/mcp monorepo, installed via uvx/pip or Docker, each with its own IAM permissions.
Tools
The managed server is built around three tools:
call_aws— runs an arbitrary AWS API call from a natural-language description.search_documentation— searches official AWS documentation.run_script— assembles and runs an automation script (Python/Bash) based on what it found in the docs.
The awslabs/mcp monorepo adds dozens of domain-specific servers — for example, for EKS (Kubernetes cluster management), Cost Explorer (spend analysis), Bedrock (model access) — connectable individually.
Agent flow
"List every S3 bucket and its size", "stop all EC2 instances tagged env=staging", "how much did I spend on RDS this month?", "set up ECS autoscaling following the official docs".
Pricing
The MCP server itself is free; you only pay for the AWS resources actually used, at standard rates.