AWS MCP Server
Related Servers
Alternatives to AWS MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables natural language control of AWS resources (EC2, Security Groups, S3, Bedrock, etc.) directly from Claude Desktop or Claude Code.MIT
- AlicenseBqualityDmaintenanceEnables Claude Desktop to interact with 57 AWS services using over 200 tools and local machine profiles. It supports multi-profile configurations and features a read-only safe mode by default to manage infrastructure like EC2, S3, and Lambda securely.100BSD 3-Clause
- FlicenseNot gradedqualityCmaintenanceEnables Claude AI to automatically audit AWS cloud resource configurations, diagnose security vulnerabilities, and generate high-availability optimization reports.-
- AlicenseAqualityCmaintenanceEnables analyzing AWS cloud costs through natural language queries, providing cost summaries, anomaly detection, idle resource identification, rightsizing recommendations, and tagging compliance via Claude.1025 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables querying AWS costs and usage data from Claude Desktop through the Cost Explorer API.1-
- AlicenseNot gradedqualityAmaintenanceEnables sending emails via Amazon SES, SMS/MMS/RCS messages through AWS End User Messaging, and sharing files via CloudFront-signed download links, all from AI assistants like Claude Code or Claude Desktop.MIT
TDQS
Scored across 10 tools
The aws_sdk_wrapper tool creates significant ambiguity as it can perform any AWS operation, overlapping with all other specialized tools. For example, ce-get_cost_and_usage and ce-get_cost_and_usage_with_resources have overlapping purposes with the wrapper, and agents may struggle to choose between them. While the specialized tools are distinct from each other, the generic wrapper undermines clear boundaries.
Most tools follow a service_verb_noun pattern (e.g., ec2-describe_instances, s3-list_buckets), but aws_sdk_wrapper deviates with a generic name and underscores. The pattern is mixed, with some using hyphens and others underscores, but it remains readable. The inconsistency is moderate, not chaotic.
With 10 tools, the count is reasonable for an AWS server, covering key services like EC2, S3, RDS, CloudWatch, and Cost Explorer. It's well-scoped, though it could be slightly expanded for broader AWS coverage. The number is appropriate, not too heavy or thin.
The server covers read operations well (describe, list, get) but lacks create, update, or delete tools for most services, creating notable gaps. For example, there are no tools to create EC2 instances or S3 buckets. The aws_sdk_wrapper can fill some gaps, but the specialized surface is incomplete for full lifecycle management.