Skip to main content
Glama
DeepaRajareddy

Redshift MCP Server

by DeepaRajareddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
REDSHIFT_HOSTYesThe Redshift host address
REDSHIFT_PORTYesThe Redshift port number5432
REDSHIFT_USERYesThe Redshift user
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

B3.4/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 reinforce these distinct roles, making tool selection straightforward for an agent.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness3/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources