Redash MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDASH_URL | Yes | Your Redash instance URL (e.g., https://redash.example.com) | |
| REDASH_API_KEY | Yes | Your Redash API key | |
| REDASH_TIMEOUT | No | Timeout for API requests in milliseconds (default: 30000) | 30000 |
| REDASH_IGNORE_SSL_ERRORS | No | Set to 'true' to ignore SSL certificate verification errors | |
| NODE_TLS_REJECT_UNAUTHORIZED | No | Set to '0' to ignore SSL certificate errors (not recommended for production) |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_queriesB | List all available queries in Redash |
| get_queryB | Get details of a specific query |
| create_queryB | Create a new query in Redash |
| update_queryC | Update an existing query in Redash |
| archive_queryA | Archive (soft-delete) a query in Redash |
| list_data_sourcesA | List all available data sources in Redash |
| execute_queryC | Execute a Redash query and return results |
| execute_raw_queryB | Execute a raw SQL query directly and return results |
| list_dashboardsB | List all available dashboards in Redash |
| get_dashboardA | Get details of a specific dashboard |
| get_visualizationB | Get details of a specific visualization |
| create_dashboardC | Create a new dashboard in Redash |
| create_widgetA | Create a new widget in a dashboard (text or visualization widget) |
| update_widgetB | Update an existing widget in a dashboard |
| delete_widgetB | Delete a widget from a dashboard |
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 15 tools
Each tool maps to a distinct resource-action pair (query, data source, dashboard, visualization, widget), with no meaningful overlap. execute_query and execute_raw_query are clearly differentiated by saved vs. raw SQL.
All tools follow a consistent verb_noun snake_case pattern (list_queries, get_query, update_query, create_widget, etc.), using standard verbs and plural/singular nouns appropriately. No mixed conventions or vague names.
With 15 tools, the server provides broad coverage of Redash's core objects without being bloated. Each tool serves a clear purpose, and the count aligns well with the typical scope for a domain-specific MCP server.
Queries have full CRUD and execution, dashboards have list/get/create but lack update/delete, and visualizations have only get (no create/update). Widgets are covered, but the missing dashboard lifecycle and visualization management create notable gaps for a management tool.