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.

DimensionAirtable MCP ServerGive AI systems read and write access to your Airtable databasesMCP ClickHouseConnect ClickHouse to your AI assistantsChEMBL MCP ServerUnofficial MCP server providing advanced access to the ChEMBL chemical database
FMRS44 / 100 · D79 / 100 · B75 / 100 · B
Reliability6 / 2012 / 2012 / 20
Security and permissions3 / 2018 / 2016 / 20
Maintenance7 / 2017 / 2014 / 20
Documentation15 / 2017 / 2018 / 20
Setup experience13 / 2015 / 2015 / 20
Best for
  • Teams looking to integrate Airtable data into AI workflows
  • Individual developers who want to use natural language to operate Airtable data
  • Scenarios requiring rapid prototyping or automation
  • 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
  • Teams requiring complex permission control or auditing (the server uses a single token)
  • Scenarios requiring real-time collaboration or complex data relationships
  • Users with high security requirements who cannot restrict network exposure
  • 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 an Airtable personal access token
  • Token needs at least schema.bases:read and data.records:read scopes
  • Optional write scopes: schema.bases:write, data.records:write, data.recordComments:read, data.recordComments:write
  • Token must have access to target bases
  • 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
  • Token leakage could allow malicious reads/writes of data
  • HTTP mode has no built-in authentication and may be vulnerable to DNS rebinding attacks
  • Delete or update operations are irreversible; mistakes may cause data loss
  • Shared tokens may exceed intended access scope
  • 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, Claude Code, Cursor, Cline, VS CodeClaude DesktopClaude Desktop
Tools15427