AWS MCP Servers

AWS publishes a large collection of independent MCP servers in the awslabs repository, each covering a single AWS service or operational area such as documentation search, infrastructure as code, EKS and ECS operations, Lambda invocation, Bedrock knowledge bases, or cost analysis. Rather than installing one monolithic server, clients add servers individually by using a uvx command that specifies exactly which server you need. All servers communicate via stdio, and servers that need access to AWS account resources read your standard AWS credentials—such as those in AWS_PROFILE—to authenticate and determine permissions.

Highlights

• Around a hundred independent servers, each scoped to a single AWS service or workflow
• Python package distribution, installed via uvx command without a separate process manager
• Stdio-only communication for integration into any MCP client environment
• Covers documentation lookup, infrastructure as code, container operations, Lambda, Bedrock, cost management, and other AWS surfaces
• Uses standard AWS credential chain for seamless authentication

This serves developers and automation teams deep in the AWS ecosystem who prefer to keep their MCP server list minimal by installing only what they need. The servers are free and distributed as open-source packages; costs apply only to the AWS services you call through them.