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 | 30000 |
| REDASH_MAX_RESULTS | No | Maximum number of results to return | 1000 |
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_queriesC | List all available queries in Redash |
| get_queryB | Get details of a specific query |
| create_queryC | Create a new query in Redash |
| update_queryC | Update an existing query in Redash |
| get_query_parametersA | Get the saved parameter definitions for a query |
| update_query_parametersB | Update a query's saved parameter definitions |
| 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_parameterized_queryB | Execute a saved parameterized query using its saved parameter definitions and defaults |
| get_query_results_csvA | Get query results in CSV format. Returns the last cached results, or optionally refreshes the query first to get the latest data. Note: Does not support parameterized queries. |
| list_dashboardsC | List all available dashboards in Redash |
| get_dashboardA | Get details of a specific dashboard |
| get_dashboard_layoutB | Get the current widget layout for a dashboard |
| get_dashboard_by_slugB | Get details of a specific dashboard by its slug |
| get_visualizationB | Get details of a specific visualization |
| execute_adhoc_queryA | Execute an ad-hoc query without saving it to Redash. Creates a temporary query that is automatically deleted after execution. |
| create_visualizationB | Create a new visualization for a query |
| update_visualizationC | Update an existing visualization |
| update_chart_visualizationB | Update chart-specific visualization options and merge them with the current Redash chart config by default |
| delete_visualizationB | Delete a visualization |
| get_schemaC | Get schema of a specific data source |
| create_dashboardB | Create a new dashboard in Redash |
| update_dashboardC | Update an existing dashboard in Redash |
| get_dashboard_parametersA | Get the current dashboard parameter values and widget mappings |
| update_dashboard_parametersB | Update dashboard parameter values and ordering |
| archive_dashboardB | Archive (soft-delete) a dashboard in Redash |
| fork_dashboardB | Fork (duplicate) an existing dashboard |
| get_public_dashboardC | Get a public dashboard by its share token |
| share_dashboardB | Share a dashboard and create a public link |
| unshare_dashboardA | Unshare a dashboard and revoke its public link |
| get_my_dashboardsA | Get dashboards created by the current user |
| get_favorite_dashboardsB | Get dashboards marked as favorite by the current user |
| add_dashboard_favoriteB | Add a dashboard to favorites |
| remove_dashboard_favoriteB | Remove a dashboard from favorites |
| get_dashboard_tagsA | Get all tags used in dashboards |
| list_alertsB | List all alerts in Redash |
| get_alertB | Get details of a specific alert |
| create_alertB | Create a new alert in Redash. Alerts notify you when a query result meets a specified condition. |
| update_alertB | Update an existing alert in Redash |
| delete_alertB | Delete an alert from Redash |
| mute_alertB | Mute an alert to temporarily stop notifications |
| get_alert_subscriptionsA | Get all subscriptions for an alert |
| add_alert_subscriptionB | Subscribe to an alert to receive notifications |
| remove_alert_subscriptionC | Unsubscribe from an alert |
| fork_queryB | Fork (duplicate) an existing query |
| get_my_queriesA | Get queries created by the current user |
| get_recent_queriesC | Get recently accessed queries |
| get_query_tagsA | Get all tags used in queries |
| get_favorite_queriesB | Get queries marked as favorite by the current user |
| add_query_favoriteB | Add a query to favorites |
| remove_query_favoriteA | Remove a query from favorites |
| list_widgetsA | List all widgets |
| get_widgetC | Get details of a specific widget |
| create_widgetB | Create a new widget on a dashboard |
| update_widgetC | Update an existing widget |
| update_widget_layoutC | Move or resize a single widget by updating its grid position |
| update_dashboard_layoutA | Move or resize multiple widgets on a dashboard in one call and report per-widget outcomes |
| get_widget_parameter_mappingsB | Get the parameter mappings for a widget |
| update_widget_parameter_mappingsB | Update a widget's parameter mappings |
| delete_widgetB | Delete a widget from a dashboard |
| list_query_snippetsA | List all reusable query snippets |
| get_query_snippetA | Get details of a specific query snippet |
| create_query_snippetA | Create a new reusable query snippet |
| update_query_snippetC | Update an existing query snippet |
| delete_query_snippetC | Delete a query snippet |
| list_destinationsA | List all alert notification destinations (email, Slack, etc.) |
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 67 tools
Each tool targets a specific resource and action, with clear distinctions even among similar operations (e.g., execute_query vs execute_adhoc_query). The descriptions further clarify any potential overlap.
All tools follow a consistent verb_noun snake_case pattern (e.g., create_dashboard, get_query, delete_alert). No mixing of conventions or vague names.
67 tools is high but appropriate for a comprehensive BI tool covering alerts, dashboards, queries, visualizations, widgets, snippets, data sources, and destinations. Each entity has a logical set of CRUD and utility tools.
The tool surface covers core workflows for alerts, dashboards, queries, and visualizations. Missing update/delete for data sources and destinations, but these are likely admin-level operations. Otherwise, no significant gaps.