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 orchestrationDBHubBytebase's official, minimalist two-tool database MCP server
FMRS48 / 100 · D74 / 100 · B
Reliability7 / 2013 / 20
Security and permissions10 / 2013 / 20
Maintenance2 / 2016 / 20
Documentation16 / 2015 / 20
Setup experience13 / 2017 / 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
  • Scenarios wanting the smallest possible tool count and lowest context-window overhead for database access
  • Cases needing to grant non-technical teammates safe, read-only database access
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 needing database administration operations (creating indexes, altering schema) rather than just querying (DBHub is positioned as a query tool, not a DBA management tool)
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 a database connection string (DSN), which may contain sensitive credentials
  • execute_sql can run arbitrary SQL (including writes) by default — must be constrained via read-only mode or the underlying database account's own permissions
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
  • Under default settings, if the connected database account has write access, execute_sql could let the assistant perform an unintended write or delete — pair with a read-only database account in production
  • The DSN contains a plaintext password — pay attention to the access permissions on wherever the config is stored
Supported clientsClaude Desktop, Cursor, fast-agent, Codex, GitHub CopilotClaude Desktop, Claude Code, VS Code, Cursor, Zed
Tools62