Get the FREE Ultimate OpenClaw Setup Guide →

dynamodb

Model Context Protocol server for managing Amazon DynamoDB resources

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio imankamyabi-dynamodb-mcp-server node build/server.js \
  --env AWS_REGION="your_region" \
  --env AWS_ACCESS_KEY_ID="your_access_key_id" \
  --env AWS_SECRET_ACCESS_KEY="your_secret_access_key"

How to use

This DynamoDB MCP Server provides a set of MCP tools for managing DynamoDB resources, including table creation, capacity management, and data operations. It exposes commands for creating and listing tables, managing global and local secondary indexes, updating provisioned capacity, and performing CRUD operations on items. You can interact with the server using the provided MCP tools to perform common DynamoDB tasks without writing raw AWS SDK calls. The server requires AWS credentials via environment variables to authenticate and authorize access to your DynamoDB resources. Once running, you can issue commands such as create_table, list_tables, describe_table, create_gsi, update_gsi, create_lsi, update_capacity, put_item, get_item, update_item, query_table, and scan_table to perform respective operations.

How to install

Prerequisites:

  • Node.js and npm installed on your machine
  • AWS credentials with permissions to manage DynamoDB resources

Install and run:

  1. Install dependencies
npm install
  1. Configure AWS credentials as environment variables (replace placeholders with your values)
export AWS_ACCESS_KEY_ID="your_access_key_id"
export AWS_SECRET_ACCESS_KEY="your_secret_access_key"
export AWS_REGION="your_region"
  1. Build the server
npm run build
  1. Start the server
npm start

This will start the MCP server using Node.js with the built server entry point. The server will listen for MCP commands and operate against your configured AWS DynamoDB resources.

Additional notes

Notes and tips:

  • Delete operations are not supported to prevent accidental data loss.
  • Ensure AWS credentials have the necessary DynamoDB permissions (CreateTable, DescribeTable, UpdateTable, PutItem, GetItem, Query, Scan, etc.).
  • The AWS_REGION must match the region where your DynamoDB tables reside.
  • If you encounter connection or permission errors, double-check the AWS credentials and IAM policies attached to the credentials used by the server.
  • When creating or updating indexes, review your provisioned capacity to avoid throttling; monitor usage and adjust read/write capacity as needed.

Related MCP Servers

Sponsor this space

Reach thousands of developers