AWS 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 |
|---|---|
| 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: 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.