Connect Amazon DynamoDB to Claude Code

Let Claude run scoped reads and writes against your Amazon DynamoDB tables. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Amazon DynamoDB to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Amazon DynamoDB, you add a Amazon DynamoDB MCP server: a small hosted service that exposes Amazon DynamoDB's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Amazon DynamoDB account. No API keys pasted into config files.

claude mcp add --transport http dynamodb https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Amazon DynamoDB once connected?

Full read-write Amazon DynamoDB access lets Claude run a query or scan against a table, inspect matching items, put a new item, update attributes on an existing one, and read capacity or index details, all within scoped IAM permissions. The lookups and item edits that used to mean the AWS console or a CLI session happen in place.

Run a query or scan against a table and summarize the matching items
Get a single item by its partition and sort key
Put a new item into a table with the attributes you specify
Update attributes on an item that matches a key you approve
Delete an item after you confirm the key it targets
Inspect a table's keys, indexes, and provisioned capacity before changing data

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Amazon DynamoDB access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Amazon DynamoDB API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Amazon DynamoDB changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Amazon DynamoDB connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Amazon DynamoDB connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Amazon DynamoDB account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Amazon DynamoDB's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Amazon DynamoDB?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Amazon DynamoDB account it signs in with. Revoking access is one click in Amazon DynamoDB.

More on the Amazon DynamoDB connector

Amazon DynamoDB connector for claude.ai Amazon Redshift + Claude Code Looker + Claude Code Metabase + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us