Skip to content
Data MCP Directory

GUIDE, read 10 Nov 2026

Snowflake data can be reached through a Snowflake-managed server, a deprecated Snowflake Labs server or a community server, and their published facts differ on every field

The directoryAll guides

Three servers, three publishers, three statuses

The Snowflake-managed MCP server is documented by Snowflake as a way for agents to retrieve data from Snowflake accounts without deploying separate infrastructure. The Snowflake Labs MCP server lives in the Snowflake-Labs/mcp repository, whose README states it is deprecated and no longer maintained and points users to the Snowflake-managed server. The community mcp-snowflake-server is a community project, not published by Snowflake, under GPL-3.0 per the GitHub API.

On the version fields, the managed server publishes no semantic version or release date; Snowflake's docs state support for MCP protocol revision 25 Nov 2025. Snowflake Labs' latest release, per its releases page and PyPI, is 1.4.2, published 15 May 2026 and titled as the release that starts deprecation. The community server is at 0.4.0 on PyPI, dated 10 Apr 2025, and its GitHub repository was last pushed 7 Oct 2025.

Where each one runs and how it is installed

Snowflake's managed server is a Snowflake object created with CREATE MCP SERVER from a YAML specification and reached at an account-scoped HTTP URL. Nothing is installed on the engineer's machine, and the server is a securable object, so it can be created, replaced and granted on like other Snowflake objects. The docs describe exposing a Cortex Agent as one client-facing tool, in which case the agent chooses among its configured Cortex Analyst, Cortex Search and custom tools for each request. The tools are declared in the specification, with types that Snowflake lists as Cortex Agent, coding agent, Cortex Search, Cortex Analyst, SQL execution and generic UDF or procedure tools.

The Snowflake Labs server is installed with uvx or Docker. Its README lists stdio as the default transport, sse as legacy and streamable-http. Tools are configured in a YAML file, and the README lists Cortex Search, Cortex Analyst and Cortex Agent services, an object manager group, a query manager group for SQL execution and a semantic manager group.

The community server is run through uvx or uv with stdio for Claude Desktop, and its README documents installing through Smithery. It is recorded as stdio only. The README does not describe a hosted mode, and the directory records no remote endpoint for it (none found on 10 Nov 2026).

How each one authenticates

Per Snowflake's docs, the managed server uses Snowflake OAuth by default with optional External OAuth, supports a PAT, and applies role-based access control per MCP server and per tool. The docs list distinct privileges: USAGE on the MCP server plus SELECT on the semantic view, or USAGE on the Cortex Search service, agent or UDF. Access to the server does not give access to tools.

The Snowflake Labs README says authentication uses the Snowflake Python connector and supports password or PAT, key pair, OAuth, SSO and MFA, and that the server honors the RBAC grants of the role used for the connection.

The community README documents Snowflake user credentials, a private key path, external browser authentication, or a connections.toml file, and its examples show plain passwords in the config. Scope then follows whatever Snowflake user those credentials belong to; the README describes no per-tool privilege layer of its own.

What tools each one lists

The community server lists eight tools: read_query, write_query, create_table, list_databases, list_schemas, list_tables, describe_table and append_insight. It also exposes a memo://insights resource, and when prefetch is enabled it exposes per-table schema summaries as resources. Per its README, describe_table returns column names, types, nullability, defaults and comments.

The managed server's Cortex Analyst tools use semantic views, which hold business definitions, and the docs say the server accepts semantic views only, not semantic models. Snowflake Labs' legacy tooling included semantic view discovery and querying plus Cortex Analyst. None of the three lists a lineage, column-lineage or object-dependency tool (none found on 10 Nov 2026 in each of the three pages read).

The three counts are not like for like. The community list is eight named tools, the Snowflake Labs entry is six groups or service types as recorded, and the managed list is six tool types in a specification. They count named functions, configuration groups and specification types, so the table gives each count with what it counts. The community README says append_insight stores insights the agent discovers, which the other two pages do not list as a tool name.

How each one documents writes and limits

The community README says write operations are disabled by default and enabled only with --allow-write, and it supports tool exclusion plus database, schema and table exclusion patterns. The Snowflake Labs README describes a sql_statement_permissions config block that allows or denies SQL statement types one by one.

For the managed server, Snowflake's docs warn that tool annotations are client hints and not security controls and that RBAC is the control. The docs also say the managed server is available in government regions except Azure US Gov Virginia and has not completed formal FedRAMP assessment.

The read dates are the same for all three, 10 Nov 2026. The Snowflake-managed and Snowflake Labs facts are Snowflake's own statements; the community facts come from the project's README, which is the publisher's own statement as well. Snowflake's docs add that the managed server serves Snowflake data only, with custom tools able to wrap UDFs and stored procedures, and Snowflake Labs' README lists Snowflake as its only coverage.

The three side by side

The table sets the recorded fields next to each other. It states no conclusion, and the order of columns is alphabetical.

For the directory's page covering all three, see MCP servers for Snowflake.

FieldCommunity mcp-snowflake-serverSnowflake Labs MCP ServerSnowflake-managed MCP server
PublisherCommunity projectSnowflake LabsSnowflake
StatusCommunity; last PyPI release 10 Apr 2025Deprecated; 1.4.2 on 15 May 2026Documented by Snowflake; MCP revision 25 Nov 2025
Transportstdiostdio default, sse, streamable-httpRemote, account-scoped HTTP URL
AuthUser credentials, key path, browser, connections.tomlConnector: password or PAT, key pair, OAuth, SSO, MFASnowflake OAuth, External OAuth, PAT
Tools8 named tools6 groups or service types, config-driven6 tool types from the specification
Write controlOff unless --allow-writePer-statement-type permissionsRBAC per MCP server and per tool
Lineage toolnone found on 10 Nov 2026none found on 10 Nov 2026none found on 10 Nov 2026

Sources

  1. Snowflake-managed MCP docs, read 10 Nov 2026
  2. Snowflake Labs MCP README, read 10 Nov 2026
  3. Snowflake Labs MCP releases, read 10 Nov 2026
  4. PyPI snowflake-labs-mcp, read 10 Nov 2026
  5. Community mcp-snowflake-server README, read 10 Nov 2026
  6. PyPI mcp-snowflake-server, read 10 Nov 2026

Last reviewed 10 Nov 2026.