Redshift MCP Server

Redshift MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server for Amazon Redshift that enables AI assistants to interact with Redshift databases.

What you get

Redshift MCP Server is a Python-based implementation of the Model Context Protocol that provides tools and resources for interacting with Amazon Redshift databases. It allows AI assistants to:

What the assistant can call

Once Redshift is connected, these are the calls the assistant has available:

• execute_sql — Executes a SQL query on the Redshift cluster
• analyze_table — Analyzes a table to collect statistics information
• get_execution_plan — Gets the execution plan with runtime statistics for a SQL query
• Prerequisites — The Prerequisites tool exposed by this server
• Resources — The Resources tool exposed by this server
• Tools — The Tools tool exposed by this server
• Dependencies — The Dependencies tool exposed by this server

Configuration and credentials

You will need 6 environment variables: RS_HOST, RS_PORT, RS_USER, RS_PASSWORD, RS_DATABASE, RS_SCHEMA. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.13 or higher - Amazon Redshift cluster - Redshift credentials (host, port, username, password, database)

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Redshift's toolset — execute_sql, analyze_table, get_execution_plan and 4 more — is a fair guide to whether it matches your workflow. It is maintained by Moonlight-CL; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the redshift mcp server does with a few real requests.