Connect Amazon Redshift to Claude Code

Let Claude run scoped queries and controlled writes against your Amazon Redshift data. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Amazon Redshift to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Amazon Redshift, you add a Amazon Redshift MCP server: a small hosted service that exposes Amazon Redshift'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 Redshift account. No API keys pasted into config files.

claude mcp add --transport http redshift 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 Redshift once connected?

Full read-write Amazon Redshift access lets Claude run parameterized queries, insert and update rows, load staged data, and apply schema or transformation changes against a cluster you control. The data exploration, cleanup, and routine modeling that used to mean hand-writing SQL in a query editor happens in conversation, with every write reviewed before it runs.

Insert or update rows in a specified table using parameterized statements
Run a query to explore a table, then propose the change it implies
Run a COPY to load data from an S3 stage into a target table after you approve it
Apply a schema change such as adding a column or creating a view
Run a transformation or backfill, showing affected row counts first
Inspect schemas, tables, and table sizes to plan a change

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 Redshift 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 Redshift API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Amazon Redshift 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 Redshift 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 Redshift 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 Redshift 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 Redshift'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 Redshift?

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 Redshift account it signs in with. Revoking access is one click in Amazon Redshift.

More on the Amazon Redshift connector

Amazon Redshift connector for claude.ai Looker + Claude Code Metabase + Claude Code Redis + 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