redash-mcp
Related Servers
Alternatives to redash-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceModel 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.4673,022 npm104MIT
- AlicenseAqualityBmaintenanceModel Context Protocol (MCP) server for Redash - manage queries, dashboards, and visualizations through AI assistants like Claude.6280 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.812 npmMIT
- FlicenseAqualityCmaintenanceA 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 24 tools
Tools are mostly distinct, with clear separation between ad-hoc run_query, saved get_query_result, and NL-driven smart_query. A few pairs—list_tables vs get_table_columns and get_query vs list_queries—require careful reading, but descriptions generally prevent misselection.
Nearly all tools follow a clean verb_noun snake_case pattern like list_queries, create_dashboard, and archive_query. The outlier is smart_query, which is named as a noun/phrase rather than an action verb, breaking the otherwise consistent convention.
At 24 tools this is a heavy toolset, falling in the 16-25 range that needs strong justification. The breadth is understandable given the Redash + BIRD intelligent-query scope, but the surface is large enough that agents will need significant selection effort.
The query lifecycle is well covered with list/get/create/update/fork/archive/run, and there is solid dashboard creation and widget placement support. However, dashboard update/delete and alert update/delete are missing, leaving notable lifecycle gaps for those resources.