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.

DimensionSupabase MCP ServerConnect Supabase to your AI assistantsMCP ClickHouseConnect ClickHouse to your AI assistantsChEMBL MCP ServerUnofficial MCP server providing advanced access to the ChEMBL chemical database
FMRS74 / 100 · B79 / 100 · B75 / 100 · B
Reliability10 / 2012 / 2012 / 20
Security and permissions15 / 2018 / 2016 / 20
Maintenance18 / 2017 / 2014 / 20
Documentation17 / 2017 / 2018 / 20
Setup experience14 / 2015 / 2015 / 20
Best for
  • Developers and teams using Supabase
  • Users wanting to integrate AI into database workflows
  • 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 not using Supabase
  • Scenarios requiring fully local and cloud-free operations (CLI has limited 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 Supabase access token (SUPABASE_ACCESS_TOKEN)
  • May require OAuth 2.1 authorization (remote)
  • Read/write by default; read-only mode available (--read-only)
  • 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
  • LLM may execute destructive operations such as dropping tables or deleting data
  • Token leakage could lead to unauthorized access
  • Remote server may log requests, posing privacy concerns
  • 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 Desktop, Cursor, WindsurfClaude DesktopClaude Desktop
Tools0427