M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionRedash MCP ServerConnect AI assistants to Redash for data queries and dashboard management.MCP Toolbox for DatabasesGoogle's official database MCP toolbox — define AI-accessible database tools via config
FMRS49 / 100 · D74 / 100 · B
Reliability8 / 2013 / 20
Security and permissions7 / 2013 / 20
Maintenance7 / 2017 / 20
Documentation14 / 2016 / 20
Setup experience13 / 2015 / 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 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.
  • 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.
  • 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 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 clientsClaude DesktopClaude Code, Gemini CLI, Zed, Antigravity
Tools270