Skip to main content
Glama
santosh07401

Redshift MCP Server

by santosh07401
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
REDSHIFT_HOSTYesThe Redshift host address
REDSHIFT_PORTNoThe Redshift port number5432
REDSHIFT_USERYesThe Redshift username
REDSHIFT_DATABASEYesThe Redshift database name
REDSHIFT_PASSWORDYesThe Redshift password

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
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
redshift_list_tablesC
List all tables in a specific schema.

Args:
    schema: The schema name (default: "public")

Returns:
    JSON list of table names
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
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
redshift_connection_statusB
Check the Redshift connection status.

Returns:
    Connection status information

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
get_tables_resourceList of available tables in the public schema.
get_status_resourceCurrent Redshift connection status.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: connection status check, table description, data sampling, table listing, and query execution. The descriptions make it unambiguous which tool to use for each database interaction task.

Naming Consistency5/5

All tools follow a perfect 'redshift_verb_noun' pattern with consistent snake_case throughout. The naming convention is predictable and immediately communicates both the domain (Redshift) and the specific action.

Tool Count5/5

Five tools is well-scoped for a database server, covering essential operations without bloat. Each tool earns its place by addressing a core database interaction need, from metadata exploration to data querying.

Completeness4/5

The toolset covers the most critical database operations well: schema exploration (list_tables, describe_table), data access (get_sample_data, query), and system status. The main gap is the lack of write/update operations (CREATE, INSERT, UPDATE, DELETE), though this might be intentional for a read-focused server.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources