Redshift MCP Server
Enables AI agents to interact with Amazon Redshift databases using natural language, providing tools to execute SQL queries, list tables, describe schemas, retrieve sample data, and monitor connection status.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Redshift MCP Server show me the first 10 rows from the users table"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Redshift MCP Server
A Model Context Protocol (MCP) server that enables AI agents to interact with Amazon Redshift using natural language.
Features
SQL Tools: Execute queries, list tables, describe schemas, get sample data.
Resources: Connection status, table list.
Sample Data: Pre-configured users, products, and orders tables.
Architecture: See DESIGN.md for system diagrams.
Related MCP server: Redshift MCP Server
🚀 Quick Start
For detailed instructions on Windows, macOS, and Linux, please refer to the SETUP.md guide.
Basic Steps (Local Testing):
Start Postgres:
docker run -d -p 5432:5432 --name postgres -e POSTGRES_PASSWORD=password postgresInstall Deps:
pip install mcp redshift-connector pandas python-dotenv psycopg2-binary sqlalchemySeed Data:
python seed_redshift.pyTest:
python test_redshift_local.py
🔧 MCP Client Configuration
Add this to your MCP client configuration (e.g., Antigravity, Claude Code, or VS Code).
"redshift-mcp": {
"command": "py",
"args": ["redshift_mcp_server.py"],
"cwd": "c:/Users/deepa/OneDrive/Desktop/workspace/redis connection",
"env": {
"REDSHIFT_HOST": "localhost",
"REDSHIFT_PORT": "5432",
"REDSHIFT_DATABASE": "postgres",
"REDSHIFT_USER": "postgres",
"REDSHIFT_PASSWORD": "password"
}
}☁️ AWS Deployment
See AWS_DEPLOYMENT.md for deployment options.
Available Tools
5 toolsredshift_connection_statusB
Check the Redshift connection status.
Returns:
Connection status information
Inputs: no named parameters. Returns: result
redshift_describe_tableB
Get the column definitions for a table.
Args:
table_name: Name of the table
schema: Schema name (default: "public")
Returns:
JSON description of columns
Inputs: table_name (required), schema. Returns: result
redshift_get_sample_dataC
Get sample rows from a table.
Args:
table_name: Name of the table
limit: Number of rows to return (default: 5)
schema: Schema name (default: "public")
Returns:
JSON sample data
Inputs: table_name (required), limit, schema. Returns: result
redshift_list_tablesC
List all tables in a specific schema.
Args:
schema: The schema name (default: "public")
Returns:
JSON list of table names
Inputs: schema. Returns: result
redshift_queryC
Execute a SQL query on Redshift and return results as JSON.
Args:
sql: The SQL query to execute
Returns:
JSON string of the query results or error message
Inputs: sql (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: connection status check, table description, data sampling, table listing, and query execution. The descriptions reinforce these distinct roles, making tool selection straightforward for an agent.
All tools follow a consistent 'redshift_' prefix with descriptive snake_case names (e.g., redshift_describe_table, redshift_query). This predictable pattern enhances readability and reduces cognitive load for users or agents.
With 5 tools, the server is well-scoped for basic Redshift database interactions, covering essential operations like connection, metadata, and querying. It could be slightly expanded to include more advanced features (e.g., data modification), but the current count is reasonable for its purpose.
The toolset covers core read-only operations (status, metadata, querying) but lacks data manipulation tools (e.g., insert, update, delete) and schema management (e.g., create table). This creates gaps for agents needing full CRUD capabilities, though basic exploration and querying are well-supported.
Related MCP Connectors
Amazon Ads, Seller Central, Vendor Central and AMC data for AI agents. Read-only by default.
Query Postgres, MySQL, SQL Server, Oracle, BigQuery, ClickHouse and Redshift from your AI client.
Query BigQuery, Snowflake, Redshift & Azure Synapse with natural language
Query, explore, and manage your databases through natural conversation.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables LLMs and AI agents to securely query and interact with Amazon Redshift databases with configurable access modes (readonly, readwrite, admin) for safe data exploration and management.-
- FlicenseAqualityDmaintenanceEnables AI agents to interact with Amazon Redshift databases using natural language to execute queries, explore schemas, and retrieve sample data.5-
- AlicenseAqualityDmaintenanceIntegrates Redshift database query capabilities with vector-based knowledgebase tools for semantic search and RAG applications. It enables users to execute SQL queries, explore database schemas, and perform hybrid semantic searches on markdown files stored in S3.7MIT
- AlicenseAqualityDmaintenanceEnables AI agents to execute SQL queries and explore Snowflake databases using natural language, with schema discovery, table inspection, and readonly mode.11571 npmMIT