Snowflake MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SNOWFLAKE_ROLE | No | Your Snowflake role | |
| SNOWFLAKE_SCHEMA | No | Your Snowflake schema | |
| SNOWFLAKE_ACCOUNT | No | Your Snowflake account identifier (e.g., abc12345.us-east-1.snowflakecomputing.com) | |
| SNOWFLAKE_DATABASE | No | Your Snowflake database | |
| SNOWFLAKE_MAX_ROWS | No | Maximum number of rows to return from queries | |
| SNOWFLAKE_PASSWORD | No | Your Snowflake password | |
| SNOWFLAKE_USERNAME | No | Your Snowflake username | |
| SNOWFLAKE_WAREHOUSE | No | Your Snowflake warehouse | |
| SNOWFLAKE_AUTHENTICATOR | No | Authentication method (e.g., externalbrowser for SSO) | |
| SNOWFLAKE_PRIVATE_KEY_PATH | No | Path to your RSA private key file (e.g., /path/to/rsa_key.p8) | |
| SNOWFLAKE_PRIVATE_KEY_PASSPHRASE | No | Passphrase for the private key (optional) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_snowflake_sql_queryA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose: executing SQL queries on Snowflake.
The single tool name 'execute_snowflake_sql_query' follows a clear verb_noun pattern. Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions.
A single tool for a Snowflake server feels too thin for the apparent scope, as it only provides raw SQL execution without any higher-level operations like listing tables, managing schemas, or handling data workflows. This is a borderline case leaning toward under-scoped.
The tool surface is severely incomplete for a Snowflake domain, lacking CRUD/lifecycle coverage. There are significant gaps such as no tools for browsing databases, tables, or schemas, and no support for common operations like data loading or user management, which will likely cause agent failures.