DynamoDB

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/pulsemcp-com-dynamodb

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

6 read · 4 write · 3 delete

Secrets

2 (API keys, tokens or passwords)

Install scripts

Not scanned yet

Runs as

Node.js package

Tools (13)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• batch_get_items

  Retrieve multiple items from one or more DynamoDB tables in a single request. Efficiently fetches up to 100 items across multiple tables using their primary keys. **Returns:** - responses: Map of table names to arrays of retrieved items - unprocessedKeys: Keys that could not be processed (retry these) **Use cases:** - Fetch multiple user profiles at once - Load related data from different tables - Resolve references in batch **Note:** Maximum 100 items per request. Unprocessed keys should be retried with exponential backoff.

• batch_write_items

  Write or delete multiple items across one or more DynamoDB tables in a single request. Efficiently performs up to 25 put or delete operations across multiple tables. **Returns:** - unprocessedItems: Requests that could not be processed (retry these) **Use cases:** - Bulk import data - Clean up multiple records - Sync data across tables - Process batch operations atomically **Note:** Maximum 25 items per request, each item up to 400KB. BatchWriteItem does not support conditional writes or returning old values. Unprocessed items should be retried with exponential backoff.

• create_table

  Create a new DynamoDB table. Creates a table with the specified primary key schema and billing mode. **Key Schema:** - HASH key (partition key): Required. Determines data distribution. - RANGE key (sort key): Optional. Enables range queries within a partition. **Attribute Types:** - S: String - N: Number (stored as string, supports arbitrary precision) - B: Binary (base64-encoded) **Returns:** - tableName: Name of created table - tableStatus: Initial status (usually CREATING) **Use cases:** - Set up new application tables - Create tables for different environments - Provision test fixture…

• delete_item

  Delete a single item from a DynamoDB table by its primary key. Removes the item if it exists. Succeeds silently if the item doesn't exist (unless conditionExpression fails). **Returns:** - attributes: The deleted item's attributes (if returnValues is "ALL_OLD" and item existed) **Use cases:** - Remove a user account - Delete expired sessions - Clean up temporary records - Remove processed queue items **Note:** Use conditionExpression to ensure you only delete items in expected states (e.g., "attribute_exists(userId)").

• delete_table

  Delete a DynamoDB table and all its data. **WARNING:** This is a destructive operation. All data in the table will be permanently deleted. **Returns:** - tableName: Name of deleted table - tableStatus: Status after deletion (usually DELETING) **Use cases:** - Clean up test tables - Remove deprecated tables - Environment teardown **Note:** - Table deletion is asynchronous. The table may take a few minutes to fully delete. - You cannot delete a table that is currently being created or updated. - Once deleted, data cannot be recovered unless you have backups.

• describe_table

  Get detailed information about a DynamoDB table. Returns comprehensive metadata including key schema, indexes, provisioned throughput, and table status. **Returns:** - tableName: Table name - tableStatus: Current status (ACTIVE, CREATING, UPDATING, DELETING) - keySchema: Primary key definition (hash and range keys) - attributeDefinitions: Attribute types for key schema - billingMode: PAY_PER_REQUEST or PROVISIONED - provisionedThroughput: Read/write capacity (if provisioned) - globalSecondaryIndexes: GSI definitions and status - localSecondaryIndexes: LSI definitions - itemCount: Approximate…

• get_item

  Retrieve a single item from a DynamoDB table by its primary key. Performs a direct lookup using the item's primary key for fast, efficient reads. **Returns:** - item: The retrieved item as a JSON object, or undefined if not found **Use cases:** - Fetch a specific user record by ID - Retrieve configuration by key - Look up a transaction by ID - Get the latest version of a document **Note:** This is the most efficient way to retrieve a single item. Use Query for multiple items with the same partition key.

• list_tables

  List all DynamoDB tables in the configured AWS region. Returns a list of table names with optional pagination support. **Returns:** - tableNames: Array of table name strings - lastEvaluatedTableName: Name to use for pagination (if more tables exist) **Use cases:** - Discover available tables in the account - Enumerate tables for backup or migration operations - Check if a specific table exists **Note:** Results are paginated. Use lastEvaluatedTableName with exclusiveStartTableName for large table lists.

• put_item

  Create a new item or replace an existing item in a DynamoDB table. Writes the entire item. If an item with the same primary key exists, it will be completely replaced. **Returns:** - attributes: Previous item values (if returnValues is "ALL_OLD" and item existed) **Use cases:** - Create a new user record - Store configuration settings - Save document versions - Update entire records **Note:** PutItem replaces the entire item. Use UpdateItem to modify specific attributes without affecting others.

• query_items

  Query items from a DynamoDB table using key conditions. Efficiently retrieves multiple items that share the same partition key, with optional sort key conditions. **Returns:** - items: Array of matching items - count: Number of items returned - scannedCount: Number of items evaluated (before filtering) - lastEvaluatedKey: Key for pagination (if more results exist) **Use cases:** - Get all orders for a customer - Retrieve messages in a time range - Find products in a category with price filters - Paginate through large result sets **Note:** Query is more efficient than Scan. Always prefer Q…

• scan_table

  Scan all items in a DynamoDB table with optional filtering. Reads every item in the table and applies optional filters. Use with caution on large tables. **Returns:** - items: Array of items (after filtering) - count: Number of items returned - scannedCount: Number of items evaluated (before filtering) - lastEvaluatedKey: Key for pagination (if more results exist) **Use cases:** - Export all data from a table - Find items when partition key is unknown - Perform analytics on entire dataset - One-time data migrations **Warning:** Scan reads every item in the table, consuming significant read…

• update_item

  Update specific attributes of an existing item in a DynamoDB table. Modifies only the specified attributes, leaving other attributes unchanged. Creates the item if it doesn't exist (upsert behavior). **Update Expression Actions:** - SET: Add or modify attributes. Example: "SET #name = :val" - REMOVE: Delete attributes. Example: "REMOVE #oldAttr" - ADD: Increment numbers or add to sets. Example: "ADD #count :one" - DELETE: Remove elements from sets. Example: "DELETE #tags :tagToRemove" **Returns:** - attributes: Item values based on returnValues setting **Use cases:** - Increment counters a…

• update_table

  Update a DynamoDB table's settings. Modify table billing mode and provisioned capacity settings. **Supported Updates:** - Switch between PAY_PER_REQUEST and PROVISIONED billing modes - Adjust read/write capacity units (for PROVISIONED tables) **Returns:** - tableName: Name of updated table - tableStatus: Status after update (usually UPDATING) **Use cases:** - Scale up capacity for high-traffic periods - Switch to on-demand billing for variable workloads - Reduce costs by switching to provisioned billing - Adjust capacity based on usage patterns **Note:** - Updates are asynchronous. Check …

Signals

Stars

81

Forks

10

Open issues

26

Contributors

4

Last commit (this folder)

Jun 14, 2026 (4 months ago)

Last release

Jun 17, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

com.pulsemcp/dynamodb

Version

0.2.7

Auth

API key

Packages

npm aws-dynamodb-mcp-server

License

MIT

Repository

github.com/pulsemcp/mcp-servers

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql