Simple Snowflake MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Override logging level (DEBUG, INFO, WARNING, ERROR, CRITICAL) | |
| CONFIG_FILE | No | Path to custom configuration file (default: config.yaml) | config.yaml |
| MCP_READ_ONLY | No | Set to 'TRUE' for read-only mode (default: TRUE) | TRUE |
| SNOWFLAKE_USER | Yes | Your Snowflake username | |
| SNOWFLAKE_SCHEMA | No | Default schema (optional) | |
| SNOWFLAKE_ACCOUNT | Yes | Your Snowflake account identifier | |
| SNOWFLAKE_DATABASE | No | Default database (optional) | |
| SNOWFLAKE_PASSWORD | Yes | Your Snowflake password | |
| SNOWFLAKE_WAREHOUSE | No | 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute-snowflake-sqlC | Execute a SQL query on Snowflake and return the result. |
| list-snowflake-warehousesB | List available Data Warehouses (DWH) on Snowflake. |
| list-databasesB | List all accessible Snowflake databases. |
| list-viewsC | List all views in a database and schema. |
| describe-viewC | Get details of a view (columns, SQL). |
| query-viewC | Query a view with an optional row limit (markdown result). |
| execute-queryB | Execute a SQL query in read-only mode (SELECT, SHOW, DESCRIBE, EXPLAIN, WITH) or not (if 'read_only' is false), result in markdown format. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize-notes | Creates a summary of all notes |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
There is significant overlap between tools, particularly 'execute-query' and 'execute-snowflake-sql' which appear to serve nearly identical purposes, both executing SQL queries on Snowflake. Additionally, 'describe-view' and 'query-view' both target views but with different outputs, which could cause confusion about when to use each. This ambiguity makes it difficult for an agent to reliably select the correct tool without careful examination of descriptions.
The naming is mixed with some consistency issues. Most tools use a verb-noun pattern (e.g., 'list-databases', 'describe-view'), but there are deviations like 'execute-snowflake-sql' which includes the platform name, unlike the simpler 'execute-query'. The use of hyphens is consistent, but the verb choices and specificity vary, leading to a readable but not fully predictable naming scheme.
With 7 tools, the count is reasonable for a Snowflake database interaction server, covering key operations like listing resources, executing queries, and managing views. It is slightly on the lower side but still well-scoped for basic database tasks, with each tool having a clear role except for the overlapping execution tools.
The tool set covers core read and list operations for Snowflake, including databases, warehouses, and views, but has notable gaps. There is no support for write operations (e.g., INSERT, UPDATE, DELETE) or schema modifications, which limits the server to querying and describing existing data. While agents can perform basic exploration, the lack of data manipulation tools makes the surface incomplete for full database management.