DynamoDB 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 |
|---|---|
| create_tableC | Creates a new DynamoDB table with specified configuration |
| update_capacityC | Updates the provisioned capacity of a table |
| put_itemC | Inserts or replaces an item in a table |
| get_itemC | Retrieves an item from a table by its primary key |
| query_tableC | Queries a table using key conditions and optional filters |
| scan_tableC | Scans an entire table with optional filters |
| describe_tableC | Gets detailed information about a DynamoDB table |
| list_tablesC | Lists all DynamoDB tables in the account |
| create_gsiC | Creates a global secondary index on a table |
| update_gsiC | Updates the provisioned capacity of a global secondary index |
| create_lsiC | Creates a local secondary index on a table (must be done during table creation) |
| update_itemC | Updates specific attributes of an item in a table |
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 12 tools
Each tool has a clearly distinct purpose targeting specific DynamoDB operations with no overlap. For example, create_table vs. describe_table vs. update_item are all unambiguous in their functions, and even similar-sounding tools like query_table and scan_table are clearly differentiated in their descriptions.
All tools follow a consistent verb_noun pattern with snake_case throughout, such as create_table, describe_table, and update_item. The naming is predictable and readable, making it easy for agents to understand the action and target resource.
With 12 tools, this server is well-scoped for DynamoDB operations, covering core CRUD, indexing, capacity management, and table lifecycle. Each tool earns its place without being overwhelming or insufficient for the domain.
The tool set provides strong coverage of DynamoDB's key operations, including table management, item CRUD, indexing, and capacity updates. A minor gap is the lack of tools for deleting tables or indexes, which could limit full lifecycle management, but core workflows are well-supported.