This community MCP server previously provided tooling for Snowflake Cortex AI, object management, and SQL orchestration. It is no longer supported.
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. The mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.
Everything the assistant can do here goes through one of these:
Cursor — Add this to your MCP settings in Cursor (Settings -> Cursor Settings -> MCP): json { "mcpServers": { "mcp-server-snowflake": { "url"Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 8 environment variables: SNOWFLAKE_MCP_ENDPOINT, SNOWFLAKE_ACCOUNT, SNOWFLAKE_USER, SNOWFLAKE_PASSWORD, SNOWFLAKE_PRIVATE_KEY, SNOWFLAKE_PRIVATE_KEY_FILE_PWD, SNOWFLAKE_HOST, SNOWFLAKE_MCP_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — Cursor — is a fair guide to whether it matches your workflow. It is maintained by Snowflake-Labs; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Cursor | Add this to your MCP settings in Cursor (Settings -> Cursor Settings -> MCP): json { "mcpServers": { "mcp-server-snowflake": { "url": "http://localhost:9000/snowflake-mcp" } } } |
{
"mcpServers": {
"snowflake-labs": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"SNOWFLAKE_MCP_ENDPOINT": "your-value",
"SNOWFLAKE_ACCOUNT": "your-value",
"SNOWFLAKE_USER": "your-value",
"SNOWFLAKE_PASSWORD": "your-value",
"SNOWFLAKE_PRIVATE_KEY": "your-value",
"SNOWFLAKE_PRIVATE_KEY_FILE_PWD": "your-value",
"SNOWFLAKE_HOST": "your-value",
"SNOWFLAKE_MCP_HOST": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SNOWFLAKE_MCP_ENDPOINT | Configuration value read at startup. | Optional |
| SNOWFLAKE_ACCOUNT | Configuration value read at startup. | Optional |
| SNOWFLAKE_USER | Configuration value read at startup. | Optional |
| SNOWFLAKE_PASSWORD | Configuration value read at startup. | Optional |
| SNOWFLAKE_PRIVATE_KEY | Credential the server authenticates with. | Yes |
| SNOWFLAKE_PRIVATE_KEY_FILE_PWD | Credential the server authenticates with. | Yes |
| SNOWFLAKE_HOST | Endpoint or connection string the server talks to. | Optional |
| SNOWFLAKE_MCP_HOST | Endpoint or connection string the server talks to. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.