| FMRS | 49 / 100 · D | 79 / 100 · B | 74 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 7 / 20 | 18 / 20 | 13 / 20 |
|---|
| Maintenance | 7 / 20 | 17 / 20 | 17 / 20 |
|---|
| Documentation | 14 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 | 15 / 20 |
|---|
| 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.
| - Teams already using ClickHouse who want AI assistants to access data directly.
- Scenarios requiring fast, read-only data queries and schema exploration.
| - Teams that want precise control over which database operations an AI can perform, rather than open arbitrary SQL execution
- Scenarios needing a unified MCP setup across multiple database engines
|
|---|
| 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.
| - Scenarios requiring write access to the database without explicit opt-in.
- Production environments with stringent security requirements that avoid default permission settings.
| - Lightweight cases that just want to run a few ad-hoc SQL queries without maintaining a tools.yaml config (a simpler single-database MCP may be a better fit)
|
|---|
| 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.
| - Requires read-only access to ClickHouse database (default).
- Optional: write access via CLICKHOUSE_ALLOW_WRITE_ACCESS.
- Optional: destructive operations via CLICKHOUSE_ALLOW_DROP.
| - Database credentials (username/password/connection string) are supplied via env vars or config
- A tool's actual permission is whatever SQL statement is defined in tools.yaml — designed for least privilege, but misconfiguration can still over-expose access
|
|---|
| 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.
| - If write access is enabled, AI might make unintended modifications.
- If DROP access is enabled, data deletion could occur accidentally.
- Credentials may be exposed via environment variables.
| - If tools.yaml defines SQL statements that allow unconstrained writes or deletes, the AI could accidentally modify data
- The prebuilt toolsets (--prebuilt) favor convenience and may expose broader query capability than a specific business actually needs — use a custom tools.yaml in production
|
|---|
| Supported clients | Claude Desktop | Claude Desktop | Claude Code, Gemini CLI, Zed, Antigravity |
|---|
| Tools | 27 | 4 | 0 |
|---|