SERVER, read 10 Nov 2026
Amazon Redshift MCP Server (AWS Labs): 8 tools, local (stdio), from AWS Labs
MCP servers for Amazon RedshiftBack to the directory
- Data tool
- Amazon Redshift
- Publisher
- AWS Labs
- Kind
- Official, Labs org
- Repository or docs
- github.com/awslabs/mcp/tree/main/src/redshift-mcp-server
- Version or commit
- 0.1.3
- Last release
- 9 Nov 2026
- Transport
- Local (stdio)
- Auth
- AWS credentials (profile/env) with IAM and Redshift Data API; database user privileges.
- Access
- Configurable
- Tools listed
- 8 named in the evidence
- Tool definitions read at
- raw.githubusercontent.com/awslabs/mcp/main/src/redshift-mcp-server/README.md
- Context weight
- 238 tokens for 8 tool definitions (8 with a description), measured from the README read
- Status
- Exists in awslabs/mcp; PyPI 0.1.3 uploaded 9 Nov 2026 (read 10 Nov 2026).
- Read
- 10 Nov 2026
In one sentence
The AWS Labs server is read-only by default with an explicit read-write opt-in, confirmation prompts and metadata discovery over the Redshift Data API.
What Amazon Redshift MCP Server (AWS Labs) exposes
8 tools are named in the evidence read on 10 Nov 2026.
list_clusters list_databases list_schemas list_tables list_columns execute_query review_cluster retrieve_skill_file
Not found in the sources read
- A lineage tool in the Redshift MCP server tool list (eight tools). Source.
The evidence on Amazon Redshift MCP Server (AWS Labs), by topic
Publisher and releases
- The server lives in the awslabs/mcp repository and PyPI lists author Amazon Web Services; awslabs.redshift-mcp-server 0.1.3 was uploaded 9 Nov 2026. (observed in the source; source, read 10 Nov 2026.)
- README calls it a server to discover, explore and query Redshift clusters and serverless workgroups. (AWS Labs's own claim; source, read 10 Nov 2026.)
Clients, auth and scoping
- The README lists 8 tools for discovery, query and cluster review, scoped to the AWS credentials in use. (AWS Labs's own claim; source, read 10 Nov 2026.)
Access and safety
- The server is read-only by default; read-write mode must be selected with ACCESS_MODE. (AWS Labs's own claim; source, read 10 Nov 2026.)
- The database user's privileges are the security boundary, not the server. (AWS Labs's own claim; source, read 10 Nov 2026.)
- In read-write mode each write prompts for confirmation via MCP elicitation unless UNSAFE_SKIP_WRITE_CONFIRMATION is set. (AWS Labs's own claim; source, read 10 Nov 2026.)
- Authentication uses AWS credentials via AWS CLI, profile or environment variables, with IAM permissions for the Data API. (AWS Labs's own claim; source, read 10 Nov 2026.)
What it reaches
- Covers Amazon Redshift provisioned clusters and serverless workgroups. (AWS Labs's own claim; source, read 10 Nov 2026.)
Lineage and impact
- Metadata tools list clusters, databases, schemas, tables and columns; review_cluster reads system views; no lineage tool. (AWS Labs's own claim; source, read 10 Nov 2026.)
Definitions, ownership and rules
- No glossary, ownership or classification tool is listed; retrieve_skill_file returns a Redshift guide covering metadata and SQL. (AWS Labs's own claim; source, read 10 Nov 2026.)
Freshness and upkeep
- Metadata is queried live from the clusters; no collection described. (AWS Labs's own claim; source, read 10 Nov 2026.)
Profile
- Runs over stdio as shown in the README client config. (AWS Labs's own claim; source, read 10 Nov 2026.)
Read next
Sources
- pypi.org/pypi/awslabs.redshift-mcp-server/json, read 10 Nov 2026
- raw.githubusercontent.com/awslabs/mcp/main/src/redshift-mcp-server/README.md, read 10 Nov 2026
Last reviewed 10 Nov 2026.