AWS MCP Server
Related Servers
Alternatives to AWS MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceA Model Context Protocol (MCP) server that enables AI assistants like Claude to interact with your AWS environment. This allows for natural language querying and management of your AWS resources during conversations. Think of better Amazon Q alternative.3295-
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables Claude to execute Python code using boto3 to query and manage AWS resources directly from conversations.124MIT
- AlicenseAqualityFmaintenanceA Model Context Protocol server implementation that enables Claude to perform AWS operations on S3 and DynamoDB services through natural language commands.23127MIT
- 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
- FlicenseNot gradedqualityFmaintenanceAn MCP server that enables Claude to generate and execute AWS CLI commands, allowing users to manage AWS resources through natural language conversations.2-
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact with Google Cloud Platform environments through natural language, allowing users to query and manage GCP resources during conversations.91,740 npm200MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: list-credentials handles credential enumeration, run-aws-code executes AWS code, and select-profile manages profile selection and authentication. There is no overlap in functionality, making tool selection unambiguous for an agent.
The tools follow a consistent verb-noun pattern with hyphens (list-credentials, run-aws-code, select-profile), which is predictable and readable. The minor deviation is that 'aws-code' includes a hyphenated noun, but this does not break the overall naming convention.
With only 3 tools, the server feels thin for an AWS integration, as it lacks core operations like managing resources (e.g., EC2, S3) or performing common AWS tasks. However, the tools cover basic setup and execution, making it borderline appropriate for a minimal scope.
The tool surface is significantly incomplete for an AWS server, as it only handles credential management and code execution without any tools for interacting with AWS services (e.g., creating instances, uploading files, querying databases). This will likely cause agent failures when attempting broader AWS operations.