M
MCP Directory CURATED DIRECTORY
868 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.

DimensionQuery MCPSafely manage Supabase through chat.MCP ClickHouseConnect ClickHouse to your AI assistantsChEMBL MCP ServerUnofficial MCP server providing advanced access to the ChEMBL chemical database
FMRS50 / 100 · D79 / 100 · B75 / 100 · B
Reliability8 / 2012 / 2012 / 20
Security and permissions12 / 2018 / 2016 / 20
Maintenance5 / 2017 / 2014 / 20
Documentation14 / 2017 / 2018 / 20
Setup experience11 / 2015 / 2015 / 20
Best for
  • Supabase developers using Cursor, Windsurf, Cline, or Claude Desktop.
  • Teams that want SQL, project management, authentication administration, and logs in one interface.
  • Development environments using local Supabase or Supabase.com-hosted projects.
  • 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 who need self-hosted Supabase support.
  • Users who need custom connection strings or Session Pooling.
  • Production teams that require ongoing maintenance, official support, or the latest features.
  • Local-only Supabase users who need Management API or Auth Admin features.
  • 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
  • Requires a database project reference and database password.
  • All operations require a QUERY_API_KEY from thequery.dev.
  • Management API operations require a Supabase personal access token.
  • Auth Admin operations require a Supabase service role key.
  • Database connections use transaction pooling; remote projects require the correct Supabase region.
  • 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
  • Safe mode permits only low-risk read-only operations by default.
  • Write operations require unsafe mode, and high-risk operations also require explicit confirmation.
  • Extreme-risk operations, such as deleting a project, are blocked.
  • Automatically generated migrations do not eliminate the risk of incorrect SQL or data loss when using high-privilege credentials.
  • The service role key and database password are highly sensitive credentials.
  • The project is no longer actively maintained, and the README points users to Supabase's official MCP server.
  • 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 clientsCursor, Windsurf, Cline, Claude DesktopClaude DesktopClaude Desktop
Tools13427