Redshift MCP Server

io.github.davidalbertonogueiraPublished by GitHub account davidalbertonogueirav1.0.5Updated Oct 24, 2026

Secure, read-only access to Amazon Redshift with schema introspection and smart sampling

VerifiedSTDIODesktop onlyDatabases

Overview

AI-generated overview

A local MCP server that gives an assistant secure, read-only access to Amazon Redshift, including schema introspection and smart sampling.

What you can do
Inspect Redshift schemas and tables to understand the database structure before querying it. Run read-only queries against Amazon Redshift data. Retrieve sampled rows from tables instead of full result sets. All access is described as read-only, so the assistant can explore and analyze data without changing it.
When to use it
Useful when an assistant needs to explore or analyze an Amazon Redshift warehouse: understanding schemas, checking sample data, or answering questions from existing tables without write access.
Requirements
Runs as a local process via the npm package @davidalbertonogueira/redshift-mcp-server over stdio. No environment variables or headers are declared, so Redshift connection details and credentials must be supplied some other way; network access to the Redshift cluster is needed.
Before you install
The server reaches a live Amazon Redshift cluster, so connection credentials will be needed and should be handled carefully. It is described as read-only, but confirm that the credentials used are themselves restricted to read-only access so the assistant cannot modify or delete data.

Installation

In SourceWeft

  1. Open Redshift MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.5LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.