DynamoDB MCP Server

Created By
imankamyabia year ago
Model Context Protocol server for managing Amazon DynamoDB resources
Overview

What is DynamoDB MCP Server?

DynamoDB MCP Server is a Model Context Protocol server designed for managing Amazon DynamoDB resources, providing tools for table management, capacity management, and data operations.

How to use DynamoDB MCP Server?

To use the server, install the dependencies, configure your AWS credentials, build the server, and start it. You can then interact with the server using various commands to manage your DynamoDB resources.

Key features of DynamoDB MCP Server?

  • Table Management: Create, list, and configure DynamoDB tables.
  • Index Management: Create and manage Global and Local Secondary Indexes.
  • Capacity Management: Update provisioned read/write capacity units.
  • Data Operations: Insert, retrieve, update, query, and scan items in tables.

Use cases of DynamoDB MCP Server?

  1. Creating and managing DynamoDB tables for applications.
  2. Scaling table capacity based on application needs.
  3. Performing CRUD operations on DynamoDB items.

FAQ from DynamoDB MCP Server?

  • Can I delete items from the tables?

No, delete operations are not supported to prevent accidental data loss.

  • Is there a limit on the number of tables I can create?

The limit is defined by AWS DynamoDB service quotas.

  • What programming language is used for this server?

The server is built using Node.js.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
imankamyabi
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago