M
MCP Directory CURATED DIRECTORY
693 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 assistantsMCP Toolbox for DatabasesGoogle's official database MCP toolbox — define AI-accessible database tools via config
FMRS48 / 100 · D79 / 100 · B74 / 100 · B
Reliability8 / 2012 / 2013 / 20
Security and permissions8 / 2018 / 2013 / 20
Maintenance10 / 2017 / 2017 / 20
Documentation10 / 2017 / 2016 / 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.
  • Teams that want precise control over which database operations an AI can perform, rather than open arbitrary SQL execution
  • Scenarios needing a unified MCP setup across multiple database engines
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.
  • Lightweight cases that just want to run a few ad-hoc SQL queries without maintaining a tools.yaml config (a simpler single-database MCP may be a better fit)
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.
  • Database credentials (username/password/connection string) are supplied via env vars or config
  • A tool's actual permission is whatever SQL statement is defined in tools.yaml — designed for least privilege, but misconfiguration can still over-expose access
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.
  • If tools.yaml defines SQL statements that allow unconstrained writes or deletes, the AI could accidentally modify data
  • The prebuilt toolsets (--prebuilt) favor convenience and may expose broader query capability than a specific business actually needs — use a custom tools.yaml in production
Supported clientsClaude DesktopClaude DesktopClaude Code, Gemini CLI, Zed, Antigravity
Tools1240