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.

DimensionArcadeDB MCP ServerBuilt-in MCP server for ArcadeDB multi-model databaseMCP ClickHouseConnect ClickHouse to your AI assistantsMCP Toolbox for DatabasesGoogle's official database MCP toolbox — define AI-accessible database tools via config
FMRS37 / 100 · D79 / 100 · B74 / 100 · B
Reliability4 / 2012 / 2013 / 20
Security and permissions5 / 2018 / 2013 / 20
Maintenance15 / 2017 / 2017 / 20
Documentation7 / 2017 / 2016 / 20
Setup experience6 / 2015 / 2015 / 20
Best for
  • AI integrations needing multi-model data support
  • Developers who want to query and manage databases directly from AI assistants
  • Applications using ArcadeDB as their backend database
  • 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
  • Users who don't need database functionality
  • MCP clients that require non-stdio transports (e.g., SSE or HTTP)
  • Users not interested in ArcadeDB itself and just want a generic database MCP
  • 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
  • Database read and write access
  • Create and manage databases, indexes, and schemas
  • Execute queries and manage data 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
  • Potential exposure of sensitive data if misconfigured
  • Database operations could lead to data loss or corruption; handle with care
  • As a database server, ensure network access control and authentication mechanisms are in place
  • 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
Tools040