@arkty/redash-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDASH_URL | Yes | Redash instance URL | |
| REDASH_API_KEY | Yes | User API key (from Redash profile settings) | |
| REDASH_TIMEOUT | No | Request timeout in ms | 30000 |
| REDASH_MAX_ROWS | No | Max rows in JSON response | 500 |
| REDASH_OUTPUT_DIR | No | Directory for CSV file output | . |
| REDASH_DEFAULT_TABLE | No | Default table name (shown in tool description) | |
| REDASH_EXTRA_HEADERS | No | Extra HTTP headers (JSON or key=value;key2=value2) | |
| REDASH_POLL_INTERVAL | No | Job polling interval in ms | 1000 |
| REDASH_MAX_POLL_ATTEMPTS | No | Max poll attempts before timeout | 120 |
| REDASH_DEFAULT_DATA_SOURCE_ID | No | Default data source ID |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_data_sourcesA | List all available Redash data sources (databases) with their IDs, names, and types |
| get_data_source_schemaA | Get the full database schema (all tables and their columns) for a data source. Use list_data_sources first to find the data_source_id. |
| get_table_infoA | Get detailed column information (names and types) for a specific table. Use search_schema if you don't know the exact table name. |
| search_schemaA | Search for tables and columns by name pattern (case-insensitive). Useful when you don't know the exact table or column name. |
| execute_adhoc_queryA | Execute a SQL query directly against a data source. No query object is created in Redash — leaves no trace. Destructive SQL (INSERT/UPDATE/DELETE/DROP etc.) is blocked. For running queries this is the DEFAULT tool. Use create_query only when user explicitly asks to save a query to Redash web UI. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The tools are mostly distinct: execute_adhoc_query handles query execution, list_data_sources handles data sources, and the remaining three handle schema discovery. There is some overlap among get_data_source_schema, get_table_info, and search_schema, but the descriptions clearly separate whole-schema, specific-table, and pattern-search use cases.
All tool names follow a consistent verb_noun snake_case pattern: execute_adhoc_query, list_data_sources, get_data_source_schema, get_table_info, and search_schema. The naming style is uniform and predictable.
With 5 tools, the server is well-scoped for its apparent purpose: running ad-hoc SQL queries and exploring database schemas. Each tool has a clear role and no redundant tools are present.
The server covers ad-hoc query execution and schema discovery well, but it references create_query for saving queries to Redash without actually providing that tool. This leaves a notable gap for users who want to persist or manage queries in the Redash web UI.