snowflake-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SNOWFLAKE_ROLE | No | Snowflake role (optional) | |
| SNOWFLAKE_USER | Yes | Snowflake username (typically email) | |
| SNOWFLAKE_SCHEMA | No | Snowflake schema name (optional) | |
| SNOWFLAKE_ACCOUNT | Yes | Snowflake account identifier (e.g., your-account.region.provider) | |
| SNOWFLAKE_DATABASE | No | Snowflake database name (optional) | |
| SNOWFLAKE_PASSWORD | Yes | Snowflake password | |
| SNOWFLAKE_WAREHOUSE | No | Snowflake warehouse name (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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_queryB | Execute a SELECT query on Snowflake |
| list_databasesA | List all available databases |
| list_schemasB | List all schemas in a database |
| list_tablesB | List all tables in a schema |
| describe_tableB | Get table schema information |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Databases | List of available Snowflake databases |
| Schemas | List of available schemas in the current database |
| Tables | List of tables in the current schema |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: browsing databases, schemas, tables, describing table schema, and executing SELECT queries. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_databases, describe_table, read_query), making them predictable and easy for an agent to interpret.
With 5 tools, the server is well-scoped for exploring a Snowflake database and executing queries. The count is neither too few nor excessive.
The tools cover the core workflow of discovering database objects and querying them. Missing operations like listing views or running DDL are minor gaps, but the set feels complete for typical read-only exploration.