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.

DimensionMCP Server MotherduckSQL analytics and data engineering for AI Assistants and IDEsMCP Toolbox for DatabasesGoogle's official database MCP toolbox — define AI-accessible database tools via config
FMRS60 / 100 · C74 / 100 · B
Reliability7 / 2013 / 20
Security and permissions13 / 2013 / 20
Maintenance12 / 2017 / 20
Documentation15 / 2016 / 20
Setup experience13 / 2015 / 20
Best for
  • Data scientists and analysts needing SQL analytics on local or remote databases
  • Developers wanting AI-assisted data engineering within IDEs
  • Teams needing to quickly explore DuckDB files
  • Users who want to incorporate MotherDuck cloud capabilities
  • 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 want a fully managed remote MCP service without local installation
  • Production environments with strict security requirements (default read-only mode still allows local filesystem access)
  • Third-party access without additional security configurations
  • 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
  • Access to local filesystem (to read DuckDB files or export data)
  • Reads environment variables for MotherDuck tokens and AWS credentials
  • Executes SQL queries in read-only mode by default; write access must be explicitly enabled
  • Optionally switches database connections at runtime (requires --allow-switch-databases)
  • 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
  • If write mode is enabled, data in databases could be modified or deleted
  • By default, when exposed to third parties, local filesystem or sensitive data may be accessed
  • MotherDuck tokens or AWS credentials could be leaked if misconfigured
  • Queries may consume significant resources (memory, CPU) or time out
  • 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 Desktop, Claude Code, Codex, Gemini CLI, Cursor, VS Code, KiroClaude Code, Gemini CLI, Zed, Antigravity
Tools50