Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

OSS Snowflake MCP Server

by Snowflake-Labsversion 1.3.5i★ –iRuns on your computer
Registry nameio.github.Snowflake-Labs/mcp

Install

Overview

Description from the maker (original English)

MCP Server for Snowflake from Snowflake Labs

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Databases & datasets
  • You need to fill in: SNOWFLAKE_PASSWORD, SNOWFLAKE_PRIVATE_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: SNOWFLAKE_ACCOUNT, SNOWFLAKE_HOST, SNOWFLAKE_USER, SNOWFLAKE_PASSWORD, SNOWFLAKE_ROLE, SNOWFLAKE_WAREHOUSE, SNOWFLAKE_PASSCODE, SNOWFLAKE_PRIVATE_KEY, SNOWFLAKE_PRIVATE_KEY_FILE, SNOWFLAKE_PRIVATE_KEY_FILE_PWD, SNOWFLAKE_MCP_HOST, SNOWFLAKE_MCP_PORT, SNOWFLAKE_MCP_ENDPOINT

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "snowflake-labs": {
      "command": "uvx",
      "args": [
        "snowflake-labs-mcp",
        "--service-config-file",
        "your-value",
        "--authenticator",
        "snowflake",
        "--transport",
        "stdio",
        "--server-host",
        "0.0.0.0",
        "--port",
        "9000",
        "--endpoint",
        "/mcp"
      ],
      "env": {
        "SNOWFLAKE_ACCOUNT": "your-value",
        "SNOWFLAKE_HOST": "your-value",
        "SNOWFLAKE_USER": "your-value",
        "SNOWFLAKE_PASSWORD": "your-value",
        "SNOWFLAKE_ROLE": "your-value",
        "SNOWFLAKE_WAREHOUSE": "your-value",
        "SNOWFLAKE_PASSCODE": "your-value",
        "SNOWFLAKE_PRIVATE_KEY": "your-value",
        "SNOWFLAKE_PRIVATE_KEY_FILE": "your-value",
        "SNOWFLAKE_PRIVATE_KEY_FILE_PWD": "your-value",
        "SNOWFLAKE_MCP_HOST": "your-value",
        "SNOWFLAKE_MCP_PORT": "your-value",
        "SNOWFLAKE_MCP_ENDPOINT": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add snowflake-labs --env SNOWFLAKE_ACCOUNT=your-value --env SNOWFLAKE_HOST=your-value --env SNOWFLAKE_USER=your-value --env SNOWFLAKE_PASSWORD=your-value --env SNOWFLAKE_ROLE=your-value --env SNOWFLAKE_WAREHOUSE=your-value --env SNOWFLAKE_PASSCODE=your-value --env SNOWFLAKE_PRIVATE_KEY=your-value --env SNOWFLAKE_PRIVATE_KEY_FILE=your-value --env SNOWFLAKE_PRIVATE_KEY_FILE_PWD=your-value --env SNOWFLAKE_MCP_HOST=your-value --env SNOWFLAKE_MCP_PORT=your-value --env SNOWFLAKE_MCP_ENDPOINT=your-value -- uvx snowflake-labs-mcp --service-config-file your-value --authenticator snowflake --transport stdio --server-host 0.0.0.0 --port 9000 --endpoint /mcp

Fill in the empty values before running it.

This one needs values on its command line, so copy the settings and fill them in.

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "snowflake-labs": {
      "command": "uvx",
      "args": [
        "snowflake-labs-mcp",
        "--service-config-file",
        "your-value",
        "--authenticator",
        "snowflake",
        "--transport",
        "stdio",
        "--server-host",
        "0.0.0.0",
        "--port",
        "9000",
        "--endpoint",
        "/mcp"
      ],
      "env": {
        "SNOWFLAKE_ACCOUNT": "your-value",
        "SNOWFLAKE_HOST": "your-value",
        "SNOWFLAKE_USER": "your-value",
        "SNOWFLAKE_PASSWORD": "your-value",
        "SNOWFLAKE_ROLE": "your-value",
        "SNOWFLAKE_WAREHOUSE": "your-value",
        "SNOWFLAKE_PASSCODE": "your-value",
        "SNOWFLAKE_PRIVATE_KEY": "your-value",
        "SNOWFLAKE_PRIVATE_KEY_FILE": "your-value",
        "SNOWFLAKE_PRIVATE_KEY_FILE_PWD": "your-value",
        "SNOWFLAKE_MCP_HOST": "your-value",
        "SNOWFLAKE_MCP_PORT": "your-value",
        "SNOWFLAKE_MCP_ENDPOINT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one needs values on its command line, so copy the settings and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "snowflake-labs": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "snowflake-labs-mcp",
        "--service-config-file",
        "your-value",
        "--authenticator",
        "snowflake",
        "--transport",
        "stdio",
        "--server-host",
        "0.0.0.0",
        "--port",
        "9000",
        "--endpoint",
        "/mcp"
      ],
      "env": {
        "SNOWFLAKE_ACCOUNT": "your-value",
        "SNOWFLAKE_HOST": "your-value",
        "SNOWFLAKE_USER": "your-value",
        "SNOWFLAKE_PASSWORD": "your-value",
        "SNOWFLAKE_ROLE": "your-value",
        "SNOWFLAKE_WAREHOUSE": "your-value",
        "SNOWFLAKE_PASSCODE": "your-value",
        "SNOWFLAKE_PRIVATE_KEY": "your-value",
        "SNOWFLAKE_PRIVATE_KEY_FILE": "your-value",
        "SNOWFLAKE_PRIVATE_KEY_FILE_PWD": "your-value",
        "SNOWFLAKE_MCP_HOST": "your-value",
        "SNOWFLAKE_MCP_PORT": "your-value",
        "SNOWFLAKE_MCP_ENDPOINT": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • SNOWFLAKE_ACCOUNT env
    Account identifier (e.g. xy12345.us-east-1)
  • SNOWFLAKE_HOST env
    Snowflake host URL
  • SNOWFLAKE_USER env
    Username for authentication
  • SNOWFLAKE_PASSWORD secret env
    Password or programmatic access token
  • SNOWFLAKE_ROLE env
    Role to use for connection
  • SNOWFLAKE_WAREHOUSE env
    Warehouse to use for queries
  • SNOWFLAKE_PASSCODE env
    MFA passcode for authentication
  • SNOWFLAKE_PRIVATE_KEY secret env
    Private key for key pair authentication
  • SNOWFLAKE_PRIVATE_KEY_FILE env
    Path to private key file
  • SNOWFLAKE_PRIVATE_KEY_FILE_PWD env
    Password for encrypted private key
  • SNOWFLAKE_MCP_HOST env
    Host address to bind the server to (default: 0.0.0.0)
  • SNOWFLAKE_MCP_PORT env
    Port number for the server to listen on (default: 9000)
  • SNOWFLAKE_MCP_ENDPOINT env
    Endpoint path for the MCP server (default: /mcp)

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Snowflake-Labs, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Databases & datasetsi

  • More stars than 0% of the other 954 servers in this category
  • Published to the registry more recently than 1% of the other 954 servers in this category
  • Basic checks equal to or better than 100% of the other 954 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is OSS Snowflake MCP Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SNOWFLAKE_PASSWORD, SNOWFLAKE_PRIVATE_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.3.5) reached the registry 12 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Supabase

by supabase

Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.

Computer or cloud★ 2,993Apache-2.0Updated yesterday
Install

MongoDB MCP Server

by mongodb-js

MongoDB Model Context Protocol Server

Runs on your computer★ 1,157Apache-2.0Updated 2 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

[DEPRECATED] Snowflake Cortex AI Model Context Protocol (MCP) Server

[!CAUTION]

This project is deprecated and no longer maintained. Please migrate to the official Snowflake MCP Server. The official server is actively developed, fully supported by Snowflake, and continues to add new features.

This community MCP server previously provided tooling for Snowflake Cortex AI, object management, and SQL orchestration. It is no longer supported. For all new and existing use cases, please use the official Snowflake MCP Server instead.


Legacy documentation (for reference only)

The MCP server supported the below capabilities:

  • [Cortex Search](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-search/cortex-search-overview): Query unstructured data in Snowflake as commonly used in Retrieval Augmented Generation (RAG) applications.
  • [Cortex Analyst](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst): Query structured data in Snowflake via rich semantic modeling.
  • [Cortex Agent](https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents): Agentic orchestrator across structured and unstructured data retrieval
  • Object Management: Perform basic operations against Snowflake's most common objects such as creation, dropping, updating, and more.
  • SQL Execution: Run LLM-generated SQL managed by user-configured permissions.
  • [Semantic View Querying](https://docs.snowflake.com/en/user-guide/views-semantic/overview): Discover and query Snowflake Semantic Views

Getting Started

Service Configuration

A simple configuration file is used to drive all tooling. An example can be seen at services/configuration.yaml and a template is below. The path to this configuration file will be passed to the server and the contents used to create MCP server tools at startup.

Cortex Services

Many Cortex Agent, Search, and Analyst services can be added. Ideal descriptions are both highly descriptive and mutually exclusive. Only the explicitly listed Cortex services will be available as tools in the MCP client.

Other Services

Other services include tooling for object management, query execution, and semantic view usage. These groups of tools can be enabled by setting them to True in the other_services section of the configuration file.

SQL Statement Permissions

The sql_statement_permissions section ensures that only approved statements are executed across any tools with access to change Snowflake objects. The list contains SQL expression types. Those marked with True are permitted while those marked with False are not permitted. Please see SQL Execution for examples of each expression type.

agent_services: # List all Cortex Agent services
  • service_name: description: > # Describe contents of the agent service

database_name: schema_name:

  • service_name: description: > # Describe contents of the agent service

database_name: schema_name: search_services: # List all Cortex Search services

  • service_name: description: > # Describe contents of the search service

database_name: schema_name:

  • service_name: description: > # Describe contents of the search service

database_name: schema_name: analyst_services: # List all Cortex Analyst semantic models/views

  • service_name: # Create descriptive name for the service semantic_model: # Fully-qualify semantic YAML model or Semantic View description: > # Describe contents of the analyst service
  • service_name: # Create descriptive name for the service semantic_model: # Fully-qualify semantic YAML model or Semantic View description: > # Describe contents of the analyst service

other_services: # Set desired tool groups to True to enable tools for that group object_manager: True # Perform basic operations against Snowflake's most common objects such as creation, dropping, updating, and more. query_manager: True # Run LLM-generated SQL managed by user-configured permissions. semantic_manager: True # Discover and query Snowflake Semantic Views and their components. sql_statement_permissions: # List SQL statements to explicitly allow (True) or disallow (False).

- All: True # To allow everything, uncomment and set All: True.

  • Alter: True
  • Command: True
  • Comment: True
  • Commit: True
  • Copy: True
  • Create: True
  • Delete: True
  • Describe: True
  • Drop: True
  • Insert: True
  • Merge: True
  • Rollback: True
  • Select: True
  • Transaction: True
  • TruncateTable: True
  • Unknown: False # To allow unknown or unmapped statement types, set Unknown: True.
  • Update: True
  • Use: True

[!NOTE]

Previous versions of the configuration file supported specifying explicit values for columns and limit for each Cortex Search service. Instead, these are now exclusively dynamic based on user prompt. If not specified, a search service's default search_columns will be returned with a limit of 10.

Connecting to Snowflake

The MCP server uses the Snowflake Python Connector for all authentication and connection methods. Please refer to the official Snowflake documentation for comprehensive authentication options and best practices.

The MCP server honors the RBAC permissions assigned to the specified role (as passed in the connection parameters) or default role of the user (if no role is passed to connect).

Connection parameters can be passed as CLI arguments and/or environment variables. The server supports all authentication methods available in the Snowflake Python Connector, including:

  • Username/password authentication
  • Key pair authentication
  • OAuth authentication
  • Single Sign-On (SSO)
  • Multi-factor authentication (MFA)
Connection Parameters

Connection parameters can be passed as CLI arguments and/or environment variables:

ParameterCLI ArgumentsEnvironment VariableDescription
Account--accountSNOWFLAKE_ACCOUNTAccount identifier (e.g. xy12345.us-east-1)
Host--hostSNOWFLAKE_HOSTSnowflake host URL
User--user, --usernameSNOWFLAKE_USERUsername for authentication
Password--passwordSNOWFLAKE_PASSWORDPassword or programmatic access token
Role--roleSNOWFLAKE_ROLERole to use for connection
Warehouse--warehouseSNOWFLAKE_WAREHOUSEWarehouse to use for queries
Passcode in Password--passcode-in-password-Whether passcode is embedded in password
Passcode--passcodeSNOWFLAKE_PASSCODEMFA passcode for authentication
Private Key--private-keySNOWFLAKE_PRIVATE_KEYPrivate key for key pair authentication
Private Key File--private-key-fileSNOWFLAKE_PRIVATE_KEY_FILEPath to private key file
Private Key Password--private-key-file-pwdSNOWFLAKE_PRIVATE_KEY_FILE_PWDPassword for encrypted private key
Authenticator--authenticator-Authentication type (default: snowflake)
Connection Name--connection-name-Name of connection from connections.toml (or config.toml) file

[!WARNING]

Deprecation Notice: The CLI arguments --account-identifier and --pat, as well as the environment variable SNOWFLAKE_PAT, are deprecated and will be removed in a future release. Please use --account and --password (or SNOWFLAKE_ACCOUNT and SNOWFLAKE_PASSWORD) instead.

Transport Configuration

The MCP server supports multiple transport mechanisms. For detailed information about MCP transports, see FastMCP Transport Protocols.

TransportDescriptionUse Case
stdioStandard input/output (default)Local development, MCP client integration
sse (legacy)Server-Sent EventsStreaming applications
streamable-httpStreamable HTTP transportContainer deployments, remote servers

Usage

# Default stdio transport

uvx snowflake-labs-mcp --service-config-file config.yaml

HTTP transport with custom endpoint

uvx snowflake-labs-mcp --service-config-file config.yaml --transport streamable-http --endpoint /my-endpoint

For containers (uses streamable-http on port 9000)

uvx snowflake-labs-mcp --service-config-file config.yaml --transport streamable-http --endpoint /snowflake-mcp

Transport Customizations

Server customizations available for sse and streamable-http transports:

ParameterCLI ArgumentEnvironment VariableDefault

| Host | --server-host | SNOWFLAKE_MCP_HOST | "0.0.0.0" | Port | --port | SNOWFLAKE_MCP_PORT | 9000 | Endpoint | --endpoint | SNOWFLAKE_MCP_ENDPOINT | /mcp | Debug Logging | --verbose | SNOWFLAKE_MCP_VERBOSE | false

Example:

export SNOWFLAKE_MCP_ENDPOINT="/my-mcp"

uvx snowflake-labs-mcp --service-config-file config.yaml --transport streamable-http

Using with MCP Clients

The MCP server is client-agnostic and will work with most MCP Clients that support basic functionality for MCP tools and (optionally) resources. Below are examples for local installation. For connecting to containerized deployments, see Connecting MCP Clients to Containers.

Claude Desktop

To integrate this server with Claude Desktop as the MCP Client, add the following to your app's server configuration. By default, this is located at:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Set the path to the service configuration file and configure your connection method:

{

"mcpServers": { "mcp-server-snowflake": { "command": "uvx", "args": [ "snowflake-labs-mcp", "--service-config-file", " /tools_config.yaml", "--connection-name", "default" ] } } }

Cursor

Register the MCP server in Cursor by opening Cursor and navigating to Settings -> Cursor Settings -> MCP. Add the below:

{

"mcpServers": { "mcp-server-snowflake": { "command": "uvx", "args": [ "snowflake-labs-mcp", "--service-config-file", " /tools_config.yaml", "--connection-name", "default" ] } } }

Add the MCP server as context in the chat.

For troubleshooting Cursor server issues, view the logs by opening the Output panel and selecting Cursor MCP from the dropdown menu.

fast-agent

Update the fastagent.config.yaml mcp server section with the configuration file path and connection name:

# MCP Servers

mcp: servers: mcp-server-snowflake: command: "uvx" args: ["snowflake-labs-mcp", "--service-config-file", " /tools_c

Only the beginning is shown; read the rest in the repo

Ask PopNx