Explore a community Redash MCP option for queries and dashboards, with a dated source check and setup references.
Data AnalysisSee source evidenceBIIndexed source: Legacy catalog; publisher unconfirmed
Source evidence
The previously indexed repository could not be read at this check. Its publisher and capabilities remain unconfirmed. The implementation below is a separate community option, not a replacement identity.
Previously indexed repository: HTTP 404 on . This is a dated observation; source availability can change.
The creator documents query execution and dashboard access through the Redash API, with REDASH_URL and REDASH_API_KEY configuration. EveryMCP has not run these tools.
Unauthenticated public HTTP GET; no MCP tools invoked. A reachable source does not establish tool behavior, security, or compatibility with your client.
Before you install: EveryMCP has not security-audited this listing or independently verified its publisher. Review the linked repository, requested permissions, deployment model, and official-registry record where applicable. How the catalog works →
The previously indexed repository returned 404 at the dated source check. Review the separately attributed community implementation and its current setup instructions before choosing a server.
Treat this as catalog metadata, not an audited command. Confirm current instructions in the linked sources before running it.
Use Cases
• Compare a community implementation
• Review query and dashboard tools
• Check deployment requirements
Tags
biredashsqldashboards
Choose a starting stack
The free planner offers three-server shortlists for five common goals. It does not automatically include Redash MCP or confirm compatibility with your environment.
Rolling out your first MCP workflow? The $49 starter kit provides a selection matrix, permission record, client example, and acceptance/rollback checklist. It does not certify Redash MCP or provide managed setup.