redash-mcp
Manage Redash queries, dashboards, widgets, alerts, visualizations, and data sources through this MCP server.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@redash-mcp list my recent queries"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
redash-mcp
Model Context Protocol (MCP) server for Redash - manage queries, dashboards, and visualizations through AI assistants like Claude.
Features
7 tools, 30 actions - compressed for minimal context usage
Full query management (list, search, create, update, archive, delete, run, adhoc, export, schedule)
Dashboard management (list, get, create, publish, delete)
Widget management with positioning (add, move, delete)
Alert management (list, get, create, update, delete)
Visualization creation (pie, line, bar, counter charts)
Data source listing
Related MCP server: redash-mcp
Installation
pip install redash-mcpOr with uvx:
uvx redash-mcpConfiguration
Environment Variables
Variable | Required | Description |
| Yes | Your Redash instance URL (e.g., |
| Yes | Your Redash API key |
| No | Request timeout in seconds (default: 30) |
Claude Code
Add to ~/.claude.json (user-level config):
{
"mcpServers": {
"redash": {
"type": "stdio",
"command": "uvx",
"args": ["redash-mcp"],
"env": {
"REDASH_URL": "https://your-redash-instance.com",
"REDASH_API_KEY": "your-api-key"
}
}
}
}Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"redash": {
"command": "uvx",
"args": ["redash-mcp"],
"env": {
"REDASH_URL": "https://your-redash-instance.com",
"REDASH_API_KEY": "your-api-key"
}
}
}
}Or if installed via pip:
{
"mcpServers": {
"redash": {
"command": "redash-mcp",
"env": {
"REDASH_URL": "https://your-redash-instance.com",
"REDASH_API_KEY": "your-api-key"
}
}
}
}Tools
redash_data_sources
List all available data sources.
redash_query
Manage Redash queries.
Action | Parameters | Description |
|
| List all queries (paginated) |
|
| Search queries by name |
|
| Get query details |
|
| Create new query |
|
| Update existing query |
|
| Archive (soft-delete) query |
|
| Permanently delete query |
|
| Execute query and wait for results |
|
| Execute SQL without saving |
|
| Export query results to file (.csv or .json) |
|
| Schedule query execution (interval in seconds) |
redash_dashboard
Manage Redash dashboards.
Action | Parameters | Description |
|
| List all dashboards |
|
| Get dashboard with widgets |
|
| Create new dashboard |
|
| Publish dashboard (remove draft) |
|
| Delete dashboard |
redash_widget
Manage dashboard widgets.
Action | Parameters | Description |
|
| Add visualization with optional position |
|
| Reposition/resize a widget |
|
| Remove widget from dashboard |
redash_alert
Manage query alerts.
Action | Parameters | Description |
| List all alerts | |
|
| Get alert details |
|
| Create alert on query result |
|
| Update alert settings |
|
| Delete alert |
redash_viz
Create visualizations.
Type | Parameters | Description |
|
| Pie chart |
|
| Line chart |
|
| Bar chart |
|
| Counter/KPI |
Note: For multiple Y columns, pass comma-separated values: y="count,total,avg"
Examples
Create a dashboard with visualizations
1. redash_data_sources() → get data_source_id
2. redash_query(action="create", name="Daily Stats", query="SELECT ...", data_source_id=1)
3. redash_viz(type="line", query_id=123, name="Trend", x="date", y="count")
4. redash_dashboard(action="create", name="My Dashboard")
5. redash_widget(action="add", dashboard_id=456, viz_id=789)
6. redash_dashboard(action="publish", id=456)Run ad-hoc query
redash_query(action="adhoc", query="SELECT COUNT(*) FROM users", data_source_id=1)Export query results
redash_query(action="export", id=123, path="/tmp/results.csv")
redash_query(action="export", id=123, path="/tmp/results.json")Search and update query
redash_query(action="search", q="daily")
redash_query(action="update", id=123, query="SELECT ... WHERE date > NOW() - INTERVAL '7 days'")Python Library Usage
You can also use redash-mcp as a Python library:
import os
os.environ["REDASH_URL"] = "https://your-redash.com"
os.environ["REDASH_API_KEY"] = "your-key"
from redash_mcp import (
list_queries, create_query, run_query,
create_dashboard, publish_dashboard,
line, bar, pie, counter,
add_widget
)
# Create query
q = create_query("My Query", "SELECT * FROM events", data_source_id=1)
# Create visualization
viz = line(q["id"], "Events Trend", x="date", y=["count"])
# Create dashboard and add widget
d = create_dashboard("My Dashboard")
add_widget(d["id"], viz["id"])
publish_dashboard(d["id"])Why redash-mcp?
Context efficient - Only 7 tools (~500 tokens) with 30 actions
Full-featured - Queries, dashboards, widgets, and visualizations
Production ready - Proper error handling and timeouts
Dual use - Works as MCP server and Python library
License
MIT
Available Tools
6 toolsredash_alertB
Manage Redash alerts. Actions: list, get, create, update, delete
Inputs: action (required), id, query_id, name, +4 more.
redash_dashboardC
Manage Redash dashboards. Actions: list, get, create, publish, delete
Inputs: action (required), id, name, page, +1 more.
redash_data_sourcesB
List all available data sources
Inputs: no named parameters.
redash_queryC
Manage Redash queries. Actions: list, search, get, create, update, archive, delete, run, adhoc, export, schedule
Inputs: action (required), id, q, name, +8 more.
redash_vizC
Create visualizations. Types: pie, line, bar, counter
Inputs: type (required), query_id (required), name (required), x, +4 more.
redash_widgetA
Manage dashboard widgets. Actions: add, move, delete
Inputs: action (required), id, dashboard_id, viz_id, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct Redash entity (alert, dashboard, data source, query, viz, widget) with clearly separate purposes, no ambiguity for an agent.
All tools follow a consistent 'redash_<resource>' pattern with snake_case; the slight plural in 'data_sources' does not break the pattern.
6 tools cover the main Redash resources without being overwhelming or too sparse, well-scoped for the domain.
Covers CRUD for alerts, dashboards, queries, and widgets, and lists data sources. Missing update/delete for visualizations is a minor gap.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Text-to-SQL MCP server: read-only queries on PostgreSQL, MySQL and SQL Server with your real schema
Related MCP Servers
- AlicenseBqualityBmaintenanceModel Context Protocol (MCP) server that integrates Redash with AI assistants like Claude, allowing them to query data, manage visualizations, and interact with dashboards through natural language.674,563 npm108MIT
- AlicenseAqualityBmaintenanceMCP server that connects Redash to Claude AI, enabling natural language data queries, dashboard management, and SQL execution.252,645 npm1MIT
- AlicenseBqualityDmaintenanceMCP server for Preset (managed Apache Superset). Manage dashboards, charts, and datasets from Claude Code and other LLM agents.591MIT
- FlicenseNot gradedqualityCmaintenanceModel Context Protocol (MCP) server that gives AI assistants a safe, correct data-analyst capability over business metrics - without raw SQL improvisation.-