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

DimensionFirebase MCP ServerMCP server that lets AI assistants work directly with Firebase servicesMCP ClickHouseConnect ClickHouse to your AI assistantsChEMBL MCP ServerUnofficial MCP server providing advanced access to the ChEMBL chemical database
FMRS54 / 100 · D79 / 100 · B75 / 100 · B
Reliability9 / 2012 / 2012 / 20
Security and permissions6 / 2018 / 2016 / 20
Maintenance11 / 2017 / 2014 / 20
Documentation15 / 2017 / 2018 / 20
Setup experience13 / 2015 / 2015 / 20
Best for
  • Developers with data already in Firebase who want AI assistants to read and write it directly
  • Users of MCP clients such as Claude Desktop, Cursor, VS Code, or Augment Code
  • Workflows combining document database, file storage, and user lookup
  • 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 Firebase project or service account credentials
  • Firebase administration tasks such as project management or function deployment
  • Environments without an MCP client or the ability to configure environment variables
  • 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 Firebase service account private key JSON file (SERVICE_ACCOUNT_KEY_PATH)
  • The service account must have proper permissions for Firestore, Storage, and Authentication services
  • Requires a Firebase Storage bucket name, either configured or defaulted
  • 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
  • Service account private keys carry broad privileges; misconfiguration or leakage can expose full data access
  • AI assistants can delete Firestore documents and upload/overwrite storage files, creating risk of unintended operations
  • The firestore_list_collections tool may trigger a Zod validation error in client logs (a known MCP SDK issue that does not affect functionality but may cause confusion)
  • Some Firestore queries require manually creating composite indexes in the Firebase Console
  • 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, Augment Code, VS Code, CursorClaude DesktopClaude Desktop
Tools12427