This project implements a Model Context Protocol (MCP) server designed specifically to interact with Amazon Redshift databases.
Redshift Utils MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. This project implements a Model Context Protocol (MCP) server designed specifically to interact with Amazon Redshift databases.
Once Redshift Utils MCP is connected, these are the calls the assistant has available:
handle_check_cluster_health — Performs a health assessment of the Redshift cluster using a set of diagnostic SQL scriptshandle_diagnose_locks — Identifies active lock contention and blocking sessions in the clusterhandle_diagnose_query_performance — Analyzes a specific query's execution performance, including plan, metrics, and historical datahandle_execute_ad_hoc_query — Executes an arbitrary SQL query provided by the user via Redshift Data API. Designed as an escape hatchhandle_get_table_definition — Retrieves the DDL (Data Definition Language) statement (SHOW TABLE) for a specific tablehandle_inspect_table — Retrieves detailed information about a specific Redshift table, covering design, storage, health, and usagehandle_monitor_workload — Analyzes cluster workload patterns over a specified time window using various diagnostic scriptsYou will need 6 environment variables: REDSHIFT_CLUSTER_ID, REDSHIFT_DATABASE, REDSHIFT_SECRET_ARN, AWS_REGION, AWS_PROFILE, AWS_DEFAULT_REGION. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Software: * Python 3.10+ * uv (recommended package manager) or pip Infrastructure & Access: * Access to an Amazon Redshift cluster. * An AWS account with permissions to use the Redshift Data API (redshift-data:*) and access the specified Secrets Manager secret (secretsmanager:GetSecretValue). * A Redshift user account whose credentials are stored in AWS Secrets Manager. This user needs
redshift-utils-mcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
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 Utils MCP's toolset — handle_check_cluster_health, handle_diagnose_locks, handle_diagnose_query_performance and 4 more — is a fair guide to whether it matches your workflow. It is maintained by vinodismyname; 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.
| Tool | What it does |
|---|---|
| handle_check_cluster_health | Performs a health assessment of the Redshift cluster using a set of diagnostic SQL scripts. |
| handle_diagnose_locks | Identifies active lock contention and blocking sessions in the cluster. |
| handle_diagnose_query_performance | Analyzes a specific query's execution performance, including plan, metrics, and historical data. |
| handle_execute_ad_hoc_query | Executes an arbitrary SQL query provided by the user via Redshift Data API. Designed as an escape hatch. |
| handle_get_table_definition | Retrieves the DDL (Data Definition Language) statement (SHOW TABLE) for a specific table. |
| handle_inspect_table | Retrieves detailed information about a specific Redshift table, covering design, storage, health, and usage. |
| handle_monitor_workload | Analyzes cluster workload patterns over a specified time window using various diagnostic scripts. |
{
"mcpServers": {
"redshift-utils": {
"command": "uvx",
"args": ["redshift-utils-mcp"],
"env": {
"REDSHIFT_CLUSTER_ID": "your-value",
"REDSHIFT_DATABASE": "your-value",
"REDSHIFT_SECRET_ARN": "your-value",
"AWS_REGION": "your-value",
"AWS_PROFILE": "your-value",
"AWS_DEFAULT_REGION": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Software: * Python 3.10+ * uv (recommended package manager) or pip Infrastructure & Access: * Access to an Amazon Redshift cluster. * An AWS account with permissions to use the Redshift Data API (redshift-data:*) and access the specified Secrets Manager secret (secretsmanager:GetSecretValue). * A Redshift user account whose credentials are stored in AWS Secrets Manager. This user needs
| Variable | Description | Required |
|---|---|---|
| REDSHIFT_CLUSTER_ID | Configuration value read at startup. | Optional |
| REDSHIFT_DATABASE | Configuration value read at startup. | Optional |
| REDSHIFT_SECRET_ARN | Credential the server authenticates with. | Yes |
| AWS_REGION | Configuration value read at startup. | Optional |
| AWS_PROFILE | Configuration value read at startup. | Optional |
| AWS_DEFAULT_REGION | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.