aws-mcp
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 |
|---|---|
| run-aws-codeC | Run AWS code |
| list-credentialsB | List all AWS credentials/configs/profiles that are configured/usable on this machine |
| select-profileA | Selects AWS profile to use for subsequent interactions. If needed, does SSO authentication |
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
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.