Developer · Local MCP server
Snowflake MCP Server
A Snowflake MCP server - SQL queries, schema exploration, and data insights for AI assistants.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.nsphung/mcp-snowflake-server- Version
- 0.14.4
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI, OCI image (Docker)
- Published
- 2026-09-24
- Updated
- 2026-09-24
- Publisher
- nsphung (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/nsphung) · how
- Listed under
- Snowflake MCP servers
- Repository
- github.com/nsphung/mcp-snowflake-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | mcp-snowflake-server-nsp | 0.14.4 | stdio |
| OCI image (Docker)runtime: docker | docker.io/nsphung/mcp-snowflake-server-nsp:0.14.4 | - | stdio |
How to connect Snowflake MCP Server
Snowflake MCP Server runs locally from a Python package published to PyPI: mcp-snowflake-server-nsp version 0.14.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx mcp-snowflake-server-nsp. It reads these environment variables: SNOWFLAKE_ACCOUNT, SNOWFLAKE_USER, SNOWFLAKE_PASSWORD (secret), SNOWFLAKE_WAREHOUSE, SNOWFLAKE_DATABASE, SNOWFLAKE_SCHEMA, SNOWFLAKE_ROLE, SNOWFLAKE_AUTHENTICATOR, SNOWFLAKE_PRIVATE_KEY_FILE, SNOWFLAKE_PRIVATE_KEY_FILE_PWD (secret), SNOWFLAKE_OAUTH_CLIENT_ID, SNOWFLAKE_OAUTH_CLIENT_SECRET (secret), SNOWFLAKE_OAUTH_TOKEN_REQUEST_URL, SNOWFLAKE_OAUTH_SCOPE and SNOWFLAKE_TOKEN (secret); set them in the client's configuration for this server.
Snowflake MCP Server runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/nsphung/mcp-snowflake-server-nsp:0.14.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e SNOWFLAKE_ACCOUNT -e SNOWFLAKE_USER -e SNOWFLAKE_PASSWORD -e SNOWFLAKE_WAREHOUSE -e SNOWFLAKE_DATABASE -e SNOWFLAKE_SCHEMA -e SNOWFLAKE_ROLE -e SNOWFLAKE_AUTHENTICATOR -e SNOWFLAKE_PRIVATE_KEY_FILE -e SNOWFLAKE_PRIVATE_KEY_FILE_PWD -e SNOWFLAKE_OAUTH_CLIENT_ID -e SNOWFLAKE_OAUTH_CLIENT_SECRET -e SNOWFLAKE_OAUTH_TOKEN_REQUEST_URL -e SNOWFLAKE_OAUTH_SCOPE -e SNOWFLAKE_TOKEN docker.io/nsphung/mcp-snowflake-server-nsp:0.14.4. It reads these environment variables: SNOWFLAKE_ACCOUNT, SNOWFLAKE_USER, SNOWFLAKE_PASSWORD (secret), SNOWFLAKE_WAREHOUSE, SNOWFLAKE_DATABASE, SNOWFLAKE_SCHEMA, SNOWFLAKE_ROLE, SNOWFLAKE_AUTHENTICATOR, SNOWFLAKE_PRIVATE_KEY_FILE, SNOWFLAKE_PRIVATE_KEY_FILE_PWD (secret), SNOWFLAKE_OAUTH_CLIENT_ID, SNOWFLAKE_OAUTH_CLIENT_SECRET (secret), SNOWFLAKE_OAUTH_TOKEN_REQUEST_URL, SNOWFLAKE_OAUTH_SCOPE and SNOWFLAKE_TOKEN (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp-snowflake-server": {
"command": "uvx",
"args": [
"mcp-snowflake-server-nsp"
],
"env": {
"SNOWFLAKE_ACCOUNT": "<value>",
"SNOWFLAKE_USER": "<value>",
"SNOWFLAKE_PASSWORD": "<secret>",
"SNOWFLAKE_WAREHOUSE": "<value>",
"SNOWFLAKE_DATABASE": "<value>",
"SNOWFLAKE_SCHEMA": "<value>",
"SNOWFLAKE_ROLE": "<value>",
"SNOWFLAKE_AUTHENTICATOR": "<value>",
"SNOWFLAKE_PRIVATE_KEY_FILE": "<value>",
"SNOWFLAKE_PRIVATE_KEY_FILE_PWD": "<secret>",
"SNOWFLAKE_OAUTH_CLIENT_ID": "<value>",
"SNOWFLAKE_OAUTH_CLIENT_SECRET": "<secret>",
"SNOWFLAKE_OAUTH_TOKEN_REQUEST_URL": "<value>",
"SNOWFLAKE_OAUTH_SCOPE": "<value>",
"SNOWFLAKE_TOKEN": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Snipara Project IntelligenceHosted MCP for source-backed project context, memory, code impact, and agent workflow continuity. | Remote · HTTP |
| Snipper MCPSearch, read, create and organise code snippets in SnipperApp 3, a native macOS snippet manager. | Local · stdio |
| Snow Leo Risk & ComplianceScreen names against OFAC, EU and UN lists; check CVEs, domain DNS and WHOIS, and public tenders. | Remote · HTTPLive check: sign-in required |
| Snowfakery MCPMCP server for authoring, analyzing, debugging, and running Snowfakery recipes. | Local · stdio |
| Snyk API & Web MCP ServerMCP server for Snyk API & Web - DAST scanning, findings management, and vulnerability triage. | Local · stdio |
| snyk.ioEasily find and fix security issues in your applications leveraging Snyk platform capabilities. | Local · stdio |
| SOC 2 ComplianceSOC 2 Type II compliance for trust services criteria (security, availability, processing. | Local · stdio |
| Social FetchPublic social-data API and live docs for AI coding agents. | Remote · HTTPLive check: sign-in required |