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 ClickHouseConnect ClickHouse to your AI assistantsChEMBL MCP ServerUnofficial MCP server providing advanced access to the ChEMBL chemical database
FMRS49 / 100 · D79 / 100 · B75 / 100 · B
Reliability8 / 2012 / 2012 / 20
Security and permissions7 / 2018 / 2016 / 20
Maintenance7 / 2017 / 2014 / 20
Documentation14 / 2017 / 2018 / 20
Setup experience13 / 2015 / 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 already using ClickHouse who want AI assistants to access data directly.
  • Scenarios requiring fast, read-only data queries and schema exploration.
  • Drug discovery and computational chemistry researchers
  • Bioinformatics teams needing ChEMBL data through AI assistants
  • Developers comfortable with Node.js or Docker
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.
  • Production settings requiring official ChEMBL support (this is unofficial)
  • Users without a Node.js or Docker environment
  • General database tasks unrelated to ChEMBL
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.
  • Outbound network access to https://www.ebi.ac.uk/chembl/api/data
  • Read-only access to public API data; no authentication credentials required
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.
  • Unofficial project with license marked NOASSERTION (README claims MIT); verify licensing yourself
  • Data accuracy depends on the ChEMBL REST API and the server's parsing may contain defects
  • 30-second request timeouts may constrain large batch queries
  • README inconsistency on tool count (22 vs 27) raises documentation reliability concerns
Supported clientsClaude DesktopClaude DesktopClaude Desktop
Tools27427