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.

DimensionSnowflake MCP Server (OSS, Deprecated)[Deprecated] Community MCP server for Snowflake Cortex AI and SQL orchestrationMCP ClickHouseConnect ClickHouse to your AI assistants
FMRS48 / 100 · D79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance2 / 2017 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2015 / 20
Best for
  • Teams already on Snowflake who need to study or reproduce a legacy MCP integration for migration purposes
  • Developers researching this project's architecture before moving to the official Snowflake MCP Server
  • Teams already using ClickHouse who want AI assistants to access data directly.
  • Scenarios requiring fast, read-only data queries and schema exploration.
Not for
  • Any new project or production deployment, since the project is officially deprecated with no further fixes or features
  • Users unfamiliar with Snowflake RBAC and SQL statement allowlisting who cannot audit the permission configuration themselves
  • Scenarios requiring write access to the database without explicit opt-in.
  • Production environments with stringent security requirements that avoid default permission settings.
Required permissions
  • Requires valid Snowflake credentials (username/password, PAT, key pair, OAuth, or SSO)
  • Server behavior is fully bound by the RBAC permissions of the connecting role, which needs access to the target databases/schemas/warehouses/Cortex services
  • Enabling SQL execution or object-management tools requires explicitly allowlisting SQL statement types (Create, Drop, Update, etc.) in the configuration file
  • Requires read-only access to ClickHouse database (default).
  • Optional: write access via CLICKHOUSE_ALLOW_WRITE_ACCESS.
  • Optional: destructive operations via CLICKHOUSE_ALLOW_DROP.
Risks and side effects
  • The project is officially marked deprecated and unmaintained, so unresolved security or functional issues may exist — not recommended for new deployments
  • Misconfigured sql_statement_permissions or an 'Unknown' statement type set to True can allow destructive SQL (DROP, DELETE, UPDATE) to execute beyond intended scope
  • Sensitive credentials (private keys, passwords) are passed via environment variables or CLI arguments, requiring careful protection of the deployment environment
  • Programmatic Access Tokens (PATs) do not evaluate secondary roles, forcing a single broadly-privileged role and coarser permission control
  • 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.
Supported clientsClaude Desktop, Cursor, fast-agent, Codex, GitHub CopilotClaude Desktop
Tools64