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
This was Snowflake Labs' open-source MCP server bringing Cortex AI, object management, SQL execution, and semantic view querying to MCP clients, but the README explicitly marks it deprecated and no longer maintained, with official guidance to migrate to Snowflake's own hosted MCP Server. Its feature scope is broad, but its permission model depends entirely on the operator correctly configuring SQL statement allowlists and Snowflake roles; misconfiguration risks destructive SQL execution, and since it is unmaintained it is unsuitable for production or new projects.
This repository (Snowflake-Labs/mcp) was a community-maintained MCP server from Snowflake Labs that connects to the Snowflake data platform, exposing Cortex Search (unstructured data retrieval for RAG), Cortex Analyst (semantic queries over structured data), Cortex Agent (orchestration across structured and unstructured sources), object management (create/drop/create-or-alter/describe/list for databases, schemas, tables, views, warehouses, compute pools, roles, stages, users, and image repositories), general SQL execution gated by sqlglot statement-type permissions, and discovery/querying of Snowflake Semantic Views. The README explicitly states the project is deprecated and no longer maintained, directing users to the official Snowflake-maintained MCP Server (documented at docs.snowflake.com). It ships as the PyPI package snowflake-labs-mcp, runs over stdio, sse (legacy), or streamable-http transport, and relies on the Snowflake Python Connector for authentication (password, PAT, key pair, MFA, SSO, OAuth).
1) Install the package via pip/uvx (snowflake-labs-mcp); 2) prepare a service configuration YAML file defining agent_services/search_services/analyst_services plus the other_services toggles and sql_statement_permissions; 3) set Snowflake connection credentials via environment variables or CLI flags (e.g. SNOWFLAKE_ACCOUNT, SNOWFLAKE_USER, SNOWFLAKE_PASSWORD); 4) point your MCP client (Claude Desktop, Cursor, fast-agent, Codex) at the uvx command with --service-config-file and --connection-name arguments; 5) optionally deploy via the provided Dockerfile or docker-compose for streamable-http transport on port 9000. Note: this project is deprecated — new users should use the official Snowflake-maintained MCP Server instead.
{"mcpServers":{"mcp-server-snowflake":{"command":"uvx","args":["snowflake-labs-mcp","--service-config-file","<path_to_file>/tools_config.yaml","--connection-name","default"]}}}