aws-helper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_ec2_instancesC | EC2 인스턴스 목록을 조회합니다 |
| get_ec2_summaryC | EC2 인스턴스 요약 정보를 제공합니다 |
| get_aws_identityB | 현재 MCP 서버가 사용하는 AWS 자격증명의 계정/사용자/Role 정보를 반환합니다 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Two tools (get_ec2_instances and get_ec2_summary) have overlapping purposes focused on EC2 instances, creating ambiguity about when to use each. While get_aws_identity is clearly distinct, the EC2 tools could easily be confused as they both retrieve EC2-related information without clear boundaries in their descriptions.
All three tools follow a consistent verb_noun naming pattern with 'get_' prefix and snake_case formatting. The naming is predictable and follows the same convention throughout the toolset.
With only 3 tools for an AWS helper server, the scope feels extremely thin. AWS has dozens of services, but this server only covers identity and EC2 instances, making it feel incomplete for a general AWS helper purpose.
For an AWS helper server, there are significant gaps in coverage. The server only provides read-only operations for identity and EC2, missing core AWS services like S3, Lambda, RDS, IAM management, and any write/update/delete operations. The surface is severely incomplete for assisting with AWS tasks.