Redshift MCP Server

Created By
aws-samplesa year ago
Overview

what is Redshift MCP Server?

Redshift MCP Server is a Model Context Protocol (MCP) server for Amazon Redshift that enables AI assistants to interact with Redshift databases, providing a set of tools for database management and query execution.

how to use Redshift MCP Server?

To use the Redshift MCP Server, clone the repository, install the necessary dependencies, set up your environment variables for Redshift connection, and start the server. Integrate it with an AI assistant by configuring the MCP settings.

key features of Redshift MCP Server?

  • Lists schemas and tables in a Redshift database
  • Retrieves table DDL scripts
  • Executes SQL queries
  • Analyzes tables to collect statistics
  • Provides execution plans for SQL queries

use cases of Redshift MCP Server?

  1. Managing and querying data in Amazon Redshift databases.
  2. Assisting AI applications in retrieving and analyzing database information.
  3. Automating database management tasks through AI integration.

FAQ from Redshift MCP Server?

  • What are the prerequisites for using Redshift MCP Server?

You need Python 3.13 or higher, an Amazon Redshift cluster, and valid Redshift credentials.

  • How do I start the server?

Use the command uv run --with mcp python-dotenv redshift-connector mcp to start the server.

  • Can I integrate it with any AI assistant?

Yes, as long as the AI assistant supports the Model Context Protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aws-samples
Star
0
Language
Python
License
MIT-0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago