MCP server for executing Snowflake queries
Most database access work still happens through a UI a human drives. Snowflake MCP server moves it into the conversation instead. MCP server for executing Snowflake queries.
A Model Context Protocol (MCP) server that enables AI agents to execute SQL queries against Snowflake databases.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 14 tools. What each one is for:
Cursor — The Cursor tool exposed by this serverexecute_query — The execute_query tool exposed by this serverexplain_query — The explain_query tool exposed by this serverConnection — The Connection tool exposed by this servertest_connection — Test the connection to Snowflake and return connection info including current user, role, warehouse, database, schema, and versionlist_databases — The list_databases tool exposed by this serverlist_schemas — The list_schemas tool exposed by this serverlist_tables — The list_tables tool exposed by this serverlist_views — The list_views tool exposed by this serverdescribe_table — Get detailed information about a table's structure including columns, types, and constraintsget_table_sample — The get_table_sample tool exposed by this serverget_table_row_count — The get_table_row_count tool exposed by this serverConfiguration is passed through the environment: SNOWFLAKE_ACCOUNT, SNOWFLAKE_USERNAME, SNOWFLAKE_AUTHENTICATOR, SNOWFLAKE_WAREHOUSE, SNOWFLAKE_DATABASE, SNOWFLAKE_SCHEMA, SNOWFLAKE_PASSWORD, SNOWFLAKE_ROLE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
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. Snowflake's toolset — Cursor, execute_query, explain_query and 11 more — is a fair guide to whether it matches your workflow. It is maintained by faressoft; 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 | The Cursor tool exposed by this server. |
| execute_query | The execute_query tool exposed by this server. |
| explain_query | The explain_query tool exposed by this server. |
| Connection | The Connection tool exposed by this server. |
| test_connection | Test the connection to Snowflake and return connection info including current user, role, warehouse, database, schema, and version. |
| list_databases | The list_databases tool exposed by this server. |
| list_schemas | The list_schemas tool exposed by this server. |
| list_tables | The list_tables tool exposed by this server. |
| list_views | The list_views tool exposed by this server. |
| describe_table | Get detailed information about a table's structure including columns, types, and constraints. |
| get_table_sample | The get_table_sample tool exposed by this server. |
| get_table_row_count | The get_table_row_count tool exposed by this server. |
| get_primary_keys | The get_primary_keys tool exposed by this server. |
| analyze_table | Analyze a table's structure, sample data, and get query suggestions. |
{
"mcpServers": {
"snowflake": {
"command": "npx",
"args": ["-y", "snowflake-mcp"],
"env": {
"SNOWFLAKE_ACCOUNT": "your-org-your-account",
"SNOWFLAKE_USERNAME": "your-username",
"SNOWFLAKE_AUTHENTICATOR": "externalbrowser",
"SNOWFLAKE_WAREHOUSE": "your-warehouse",
"SNOWFLAKE_DATABASE": "your-database",
"SNOWFLAKE_SCHEMA": "your-schema"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SNOWFLAKE_ACCOUNT | Configuration value read at startup. | Optional |
| SNOWFLAKE_USERNAME | Configuration value read at startup. | Optional |
| SNOWFLAKE_AUTHENTICATOR | Configuration value read at startup. | Optional |
| SNOWFLAKE_WAREHOUSE | Configuration value read at startup. | Optional |
| SNOWFLAKE_DATABASE | Configuration value read at startup. | Optional |
| SNOWFLAKE_SCHEMA | Configuration value read at startup. | Optional |
| SNOWFLAKE_PASSWORD | Configuration value read at startup. | Optional |
| SNOWFLAKE_ROLE | Configuration value read at startup. | 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.