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 |
|---|---|
| s3_bucket_createC | Create a new S3 bucket |
| s3_bucket_listB | List all S3 buckets |
| s3_bucket_deleteC | Delete an S3 bucket |
| s3_object_uploadC | Upload an object to S3 |
| s3_object_deleteC | Delete an object from S3 |
| s3_object_listC | List objects in an S3 bucket |
| s3_object_readC | Read an object's content from S3 |
| dynamodb_table_createC | Create a new DynamoDB table |
| dynamodb_table_describeC | Get details about a DynamoDB table |
| dynamodb_table_listB | List all DynamoDB tables |
| dynamodb_table_deleteC | Delete a DynamoDB table |
| dynamodb_table_updateC | Update a DynamoDB table |
| dynamodb_item_putC | Put an item into a DynamoDB table |
| dynamodb_item_getC | Get an item from a DynamoDB table |
| dynamodb_item_updateC | Update an item in a DynamoDB table |
| dynamodb_item_deleteC | Delete an item from a DynamoDB table |
| dynamodb_item_queryC | Query items in a DynamoDB table |
| dynamodb_item_scanC | Scan items in a DynamoDB table |
| dynamodb_batch_getC | Batch get multiple items from DynamoDB tables |
| dynamodb_item_batch_writeC | Batch write operations (put/delete) for DynamoDB items |
| dynamodb_describe_ttlC | Get the TTL settings for a table |
| dynamodb_update_ttlC | Update the TTL settings for a table |
| dynamodb_batch_executeC | Execute multiple PartiQL statements in a batch |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| AWS Operations Audit Log | A log of all AWS operations performed through this server |
TDQS
Scored across 23 tools
Every tool has a clearly distinct purpose with no ambiguity. The DynamoDB tools are precisely scoped to specific operations (batch_execute, batch_get, describe_ttl, etc.), and S3 tools are similarly well-defined (bucket_create, object_read, etc.). There is no overlap where an agent would struggle to choose between tools.
All tool names follow a consistent pattern of service_operation format (e.g., dynamodb_item_get, s3_object_upload). The naming is uniformly snake_case with clear verbs (get, put, delete, list, create, update) that match the operations precisely, making it highly predictable and readable.
With 23 tools, the count is slightly high but reasonable for covering two major AWS services (DynamoDB and S3). It provides comprehensive operations for each service, though it might feel heavy for a single server. The scope is well-defined, and each tool serves a distinct function, justifying its inclusion.
The tool set offers complete CRUD/lifecycle coverage for both DynamoDB and S3 domains. For DynamoDB, it includes table management (create, describe, list, update, delete) and item operations (get, put, update, delete, query, scan, batch operations, TTL). For S3, it covers bucket management (create, list, delete) and object operations (upload, read, list, delete). No obvious gaps exist for core workflows.