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.

DimensionChroma MCP ServerModel Context Protocol server for Chroma, providing database capabilities for AI models.MCP ClickHouseConnect ClickHouse to your AI assistantsChEMBL MCP ServerUnofficial MCP server providing advanced access to the ChEMBL chemical database
FMRS48 / 100 · D79 / 100 · B75 / 100 · B
Reliability8 / 2012 / 2012 / 20
Security and permissions8 / 2018 / 2016 / 20
Maintenance10 / 2017 / 2014 / 20
Documentation10 / 2017 / 2018 / 20
Setup experience12 / 2015 / 2015 / 20
Best for
  • Vector database scenarios that need integration with MCP-compatible clients like Claude.
  • Developers and teams who want to self-host Chroma and unify APIs.
  • AI applications that require persistent or cloud-hosted vector storage.
  • 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
  • Not suitable for non-vector database use cases.
  • Not for applications needing relational queries or complex transactions.
  • Not ideal for scenarios with high data privacy requirements that can't tolerate external API calls (when using external embedding functions).
  • 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
  • File system access (for persistent client) to store data.
  • Network access (for HTTP or cloud clients) to connect to remote Chroma instances or external embedding APIs.
  • API keys in environment variables or config files (e.g., Cohere, OpenAI) to call external embedding models.
  • 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
  • External embedding APIs may send data to third-party services, posing data leakage risks.
  • Self-hosted HTTP clients without proper authentication may expose sensitive data.
  • Persistent clients require write permissions and backup for the data directory.
  • 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
Tools12427