Amazon Redshift MCP Server

AWS Labs · Data & Analytics Infrastructure

Community

AWS Labs open-source MCP server for Amazon Redshift. Run SQL analytics, inspect schemas, and generate reports from any MCP client.

data warehousesqlawsreporting

Status

Community

Auth

API key

Hosting

Local

Community rating

Not rated yet

Open documentation →

Rate this server

How to connect Amazon Redshift MCP Server

Step 1

Local server — run it on your machine

Amazon Redshift MCP Server runs locally over stdio. You need Node.js (for npx) or Python (for uvx) installed, then add the command below to your client's MCP config file.

Command

uvx awslabs.redshift-mcp-server

Client config snippet

{
  "mcpServers": {
    "redshift-mcp": {
      "command": "uvx",
      "args": [
        "awslabs.redshift-mcp-server"
      ]
    }
  }
}

Step 2

Authenticate with API key

Create a key in the vendor's dashboard and store it as an environment variable in your client config — never paste it into a chat window.

Step 3

Verify, then widen access

Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.

Prompts that use this server

Starter prompts from the Practice Stacks that rely on Data & Analytics Infrastructure.

Custom reporting query brief

A firm-level answer pulled from your warehouse.

Portfolio Reporting & PerformanceData & Analytics InfrastructureCustody & Clearing

Read-only: answer <question, e.g. AUM by custodian and household size> from my analytics warehouse, then spot-check the answer against the live custodial data for two or three sample accounts. Show the SELECT query you ran, the row counts, the result table, and a reconciliation line comparing warehouse totals to custodian totals with any variance called out. Use SELECT only — no inserts, updates, deletes or schema changes — and do not place or modify anything at the custodian. If a table or account you need is missing, say so instead of approximating.

Guardrail · Read-only credentials only. Never connect a warehouse with write access to a chat tool.

Warehouse schema map

A plain-English map of what data you actually have.

Data Infrastructure (Builder / Enterprise)Data & Analytics InfrastructureWealth Platforms

Read-only: map the warehouse schemas and tables relevant to <domain, e.g. client holdings> — table, purpose, grain, row count and how tables join — then trace each one back to the upstream wealth platform or custodial API field that feeds it. Output a lineage table of Warehouse table.column / Upstream source field / Grain / Last loaded, and flag tables with no identifiable upstream source or with fields the source no longer provides. Use metadata and SELECT queries only — no DDL, no writes, no schema changes.

Guardrail · Read-only credentials. Never connect a warehouse with DDL rights to a chat tool.

Data quality profile

Nulls, duplicates and outliers in the tables you rely on.

Data Infrastructure (Builder / Enterprise)Data & Analytics InfrastructureMarket & Financial Data

Read-only: profile <table or dataset> — null rates by column, duplicate keys, value ranges and obvious outliers — then validate a sample of its prices, identifiers or corporate-action fields against a market-data source for the same dates. Show the SELECT queries you ran, the results, and a comparison table of warehouse value vs. market-data value vs. variance. Do not write, delete or correct any data. Recommend fixes as a list for my engineer to review.

Guardrail · Read-only. Corrections belong in your pipeline, with review and version control.

Read the full connection guide →