aws-mcp
Related Servers
Alternatives to aws-mcp
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceA Model Context Protocol server allowing Claude AI to interact with AWS resources through natural language, enabling users to query and manage AWS services without using the traditional AWS Console or CLI.36-
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables Claude to execute Python code using boto3 to query and manage AWS resources directly from conversations.124MIT
- AlicenseNot gradedqualityFmaintenanceA lightweight service that enables AI assistants to execute AWS CLI commands through the Model Context Protocol (MCP), allowing AI tools to retrieve AWS documentation and interact with AWS services.186MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables AI assistants to perform comprehensive AWS security analysis through natural language queries, bridging AI with AWS security services.2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects AI assistants like Claude to AWS security services, allowing them to autonomously query, inspect, and analyze AWS infrastructure for security issues and misconfigurations.84Apache 2.0
- AlicenseAqualityFmaintenanceA Model Context Protocol server implementation that enables Claude to perform AWS operations on S3 and DynamoDB services through natural language commands.23127MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: list-credentials handles credential enumeration, run-aws-code executes AWS code, and select-profile manages profile selection and authentication. An agent can easily differentiate between these three functions.
All tool names follow a consistent verb-noun pattern with hyphens (list-credentials, run-aws-code, select-profile), making them predictable and readable throughout the set.
With only 3 tools, the server feels under-scoped for AWS operations, which typically involve many services and actions. This limited set may not support common workflows like managing resources (e.g., S3, EC2) or performing CRUD operations, making it insufficient for the domain.
The tool set is severely incomplete for AWS functionality, lacking core operations such as creating, updating, or deleting resources, querying service status, or handling specific AWS services. This will cause significant agent failures in typical AWS tasks.