redash-mcp
Related Servers
Alternatives to redash-mcp
No user-submitted related servers found.
Related 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,448 npm108MIT
- AlicenseAqualityDmaintenanceModel Context Protocol (MCP) server for Redash - manage queries, dashboards, and visualizations through AI assistants like Claude.699 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that connects AI assistants to Redash, enabling listing of assets, read-only query execution, dashboard inspection, and alert management through the Redash API.MIT
- AlicenseAqualityDmaintenanceA database-agnostic MCP server that enables natural language queries to your database through Claude or Copilot, automatically writing and executing SQL.85 npmMIT
- FlicenseAqualityDmaintenanceA unified MCP server that lets Claude query any SQLite database and build live Streamlit dashboards — all from a single conversation.101-
- AlicenseNot gradedqualityBmaintenanceAn MCP server that connects to open data portals like CKAN and Socrata, enabling natural language querying of datasets via Claude.MIT
TDQS
Scored across 25 tools
Core Redash operations are well separated by resource and action, and run_query vs get_query_result vs smart_query are explicitly differentiated in descriptions. The main ambiguity is the smart-query meta-tool cluster (few-shot examples, feedback, query evaluation, keyword maps, BIRD config), whose boundaries are related and could cause misselection.
Almost all tools use consistent snake_case with a verb_noun pattern (list_queries, create_dashboard, get_alert, manage_keyword_map). Minor deviations are smart_query, which is not verb-led, and get_bird_config, but the overall convention remains predictable.
At 25 tools this is at the heavy end for an MCP server and forces agents to choose among many related operations. The core Redash tools are reasonable, but the smart-query learning/evaluation/config tools inflate the surface and make the set feel borderline over-scoped.
The server covers important workflows: query discovery, execution, creation/update/fork/archive, dashboards/widgets, alerts, schema inspection, and ad-hoc SQL. However, notable lifecycle gaps remain, including no dashboard update/delete, no alert update/delete, no widget/visualization removal, and data sources are only listable.