Best for
- Teams that already operate Redash and want MCP access to its analytics features.
- MCP clients requiring query execution, schema discovery, and dashboard management.
- Operators who need OpenTelemetry visibility into MCP and Redash requests.
R
Redash MCP Server
Community
Connect AI assistants to Redash for data queries and dashboard management.
GitHub source repository ↗
49FMRS · D
Based on the README: this is a non-official Redash MCP server supporting stdio and stateless Streamable HTTP, with broad query, schema, dashboard, and visualization management. Check API-key permissions, data exposure, and gateway authentication before deployment.
Redash MCP Server exposes Redash queries, data sources, schemas, dashboards, and visualizations through the Redash API to MCP clients. It supports ad-hoc and saved parameterized query execution, query creation, updating and archiving, schema discovery, dashboard layout and parameter mapping management, and chart-specific visualization updates.
Tools
list_queries
List available queries in Redash.
get_query
Get details for a specific query.
create_query
Create a query in Redash.
update_query
Update an existing query.
get_query_parameters
Inspect saved query parameter definitions.
update_query_parameters
Update saved query parameter definitions.
archive_query
Archive, or soft-delete, a query.
list_data_sources
List available data sources.
execute_query
Execute a query and return results, with optional maxAge.
execute_parameterized_query
Execute a saved parameterized query with typed value coercion, saved defaults, and optional maxAge.
execute_adhoc_query
Execute an ad-hoc query without saving it to Redash.
get_query_results_csv
Get query results as CSV, with optional refresh for current data.
get_schema
Retrieve a data source schema with paginated tables and columns.
list_dashboards
List available dashboards.
get_dashboard
Get dashboard details and visualizations.
get_dashboard_layout
Inspect dashboard widget positions, sizes, and visibility.
get_visualization
Get details for a specific visualization.
get_dashboard_parameters
Inspect dashboard parameter values and widget mappings.
update_dashboard_parameters
Update dashboard parameter values and ordering.
update_dashboard_layout
Move or resize multiple widgets in one call.
update_widget_layout
Move or resize a single widget.
get_widget_parameter_mappings
Inspect a widget's parameter mappings.
update_widget_parameter_mappings
Update a widget's parameter mappings.
create_visualization
Create a visualization for a query.
update_visualization
Update an existing visualization.
update_chart_visualization
Update chart-specific options such as series type, column mapping, series options, legend, and axis settings.
delete_visualization
Delete a visualization.
Setup
Prepare Node.js 22.13 or later, Corepack, access to a Redash instance, and a Redash API key. Configure Claude Desktop with npx and set REDASH_URL and REDASH_API_KEY. Alternatively, clone the repository and run corepack enable, pnpm install, pnpm run build, and pnpm start. The default transport is stdio; set MCP_TRANSPORT=http for stateless Streamable HTTP.
claude_desktop_config.json
{"mcpServers":{"redash":{"command":"npx","args":["-y","@suthio/redash-mcp"],"env":{"REDASH_API_KEY":"your-api-key","REDASH_URL":"https://your-redash-instance.com"}}}}
Fit and risk
Not for
- Users without a Redash instance or API key.
- Use cases requiring direct database access without the Redash API.
- Deployments that would expose the HTTP listener directly to the internet.
Required permissions
- Access to a Redash instance is required.
- REDASH_API_KEY is required; the server manages the Authorization header using the Key scheme.
- Depending on the tools used, the API key may permit reading, creating, updating, or archiving queries and managing dashboards and visualizations.
Risks and side effects
- Query results, SQL, descriptions, visualizations, and CSV data may contain sensitive business information.
- When OTel message-content capture is enabled, query arguments, results, and error content may be sent to telemetry backends.
- HTTP Host and Origin allowlists do not authenticate MCP clients; run the server behind an authenticated gateway or reverse proxy.
- Archiving is a soft delete, while visualization deletion and query, layout, or parameter updates still modify Redash state.
Troubleshooting
- Verify that REDASH_URL and REDASH_API_KEY are set and that the key can access the target Redash instance.
- Verify Node.js is at least 22.13 and Corepack is enabled.
- In stdio mode, ensure logs go to stderr and are not treated as MCP output.
- In HTTP mode, check MCP_TRANSPORT, host, port, path, and Host/Origin allowlists; the default endpoint is 127.0.0.1:3000/mcp.
- HTTP mode does not provide a standalone GET SSE stream; use POST /mcp.
- For large schemas, paginate get_schema with page, pageSize, search, and nextPage.
Use cases
Discovering and executing Redash queries through an AI assistant.
Running saved parameterized queries with typed values and saved defaults.
Exploring data-source schemas to support query writing.
Creating and maintaining queries, dashboard layouts, and visualizations.
Supported clients
Claude DesktopFull support