Delv
Official (Vendor)Active· 1mo4.3by Snowflake

Snowflake

Snowflake MCP for warehouse queries. Enterprise data teams use it to let Claude run analytical SQL against the lake.

A
Safety & Trust

Delv Safety Grade: A

Score 83/100 · assessed 2026-04-28

Maintainer95
Permissions65
Supply chain85
Transparency80
Incidents100

Snowflake's official MCP server provides Claude with direct SQL query access to your data warehouse. The maintainer score is excellent given Snowflake's enterprise standing and active development in their Labs repository. Permissions are moderately scoped: it can read and write to your warehouse (SQL queries can modify data via INSERT/UPDATE/DELETE), and requires network access plus credential environment variables. Supply chain is solid via PyPI distribution, though the uvx install method and YAML config file add minor complexity. Transparency is good with open source code and clear documentation, though being in a Labs repo means slightly less polish than mainline products. No known security incidents. The main risk is the breadth of database access granted once credentials are provided.

Lethal Trifecta (prompt-injection exposure)

ONE OF THREE
Private dataYes
Reads secrets, credentials, private files
Untrusted inputNo
Ingests web pages, PRs, issues, emails
External commsNo
Can send data outbound

Same shape as BigQuery.

Green flags

  • Official Snowflake vendor implementation with enterprise backing
  • Open source on GitHub with visible code and issue tracking
  • Standard PyPI distribution via snowflake-labs-mcp package
  • Scoped to Snowflake API, no filesystem or shell access
  • Active maintenance in Snowflake-Labs organization

Red flags

  • Full warehouse access with write capabilities via SQL execution
  • Credentials stored in environment variables without additional auth layers
  • Labs repo suggests experimental status, potentially less security review
  • YAML config file requirement adds configuration complexity

Permissions requested

DB readDB writeOutbound networkAccess secrets
Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Install

uvx snowflake-labs-mcp --service-config-file config.yaml
Env vars needed: SNOWFLAKE_ACCOUNTSNOWFLAKE_USERSNOWFLAKE_PASSWORD

Review

This is Snowflake's official MCP server for running SQL queries against your data warehouse from Claude. You authenticate with account credentials, and Claude can then execute analytical queries, inspect schemas, and pull results directly into the conversation. It's built for data teams who want to let Claude act as a conversational query layer over their Snowflake instance. I'd reach for this when I'm doing exploratory analysis and don't want to context-switch between Claude Desktop and the Snowflake web console. Ask Claude to "show me revenue by region for Q4" and it writes the SQL, runs it, and formats the results. The workflow shines when you're iterating on queries or need to explain data patterns to non-technical stakeholders. Claude can refine queries based on your feedback without you touching the SQL. The setup is straightforward if you already have Snowflake credentials. You drop three environment variables into your Claude Desktop config and you're running queries. The server handles connection pooling and query execution. It doesn't try to be clever about caching or query optimisation, it just runs what Claude asks for. Quirks: this is read-only by design, which is sensible but means you can't use it for data transformations or table creation. Claude also can't see query plans or performance metrics, so it's not useful for optimisation work. The server assumes you trust Claude with your warehouse credentials, which is fine for personal projects but needs careful thought in a team setting. There's no row limit enforcement in the server itself, so a poorly scoped query could pull back a massive result set. Skip this if you're not already a Snowflake customer or if your use case is just occasional lookups. The value is in the conversational iteration, not one-off queries. Also skip if you need write access or want to use this in production pipelines. This is an analysis tool, not an orchestration layer.
Verdict

Install this if you're a Snowflake user doing regular exploratory analysis and want Claude as a query assistant. Skip it if you need write access, production-grade query controls, or aren't already paying for Snowflake. The official vendor stamp means it'll stay current with Snowflake's API changes.

Good at

  • Official Snowflake build means it tracks API changes and security updates without community lag.
  • Conversational query refinement is faster than switching between Claude and the Snowflake console for exploratory work.
  • Read-only by design prevents accidental data mutations during analysis sessions.
  • Handles authentication and connection pooling so you don't write boilerplate.

Watch out

  • No write access means you can't use it for transformations or table creation workflows.
  • Requires hardcoded credentials in config, which is awkward for team environments without a secrets manager.
  • No built-in row limits or cost controls, so a vague query can run up warehouse charges.
  • Only supports Claude Desktop and Cursor officially, other hosts need manual configuration.
  • No query plan or performance visibility, so it's not useful for optimisation tasks.

Getting started

1. Clone the repository from https://github.com/Snowflake-Labs/mcp and follow the build instructions in the README to compile the server binary. 2. Add the server to your Claude Desktop config with SNOWFLAKE_ACCOUNT, SNOWFLAKE_USER, and SNOWFLAKE_PASSWORD as environment variables, pointing to the compiled binary. 3. Restart Claude Desktop and ask it to "list databases in my Snowflake account" to verify the connection works. 4. Start with read-only queries on small tables to confirm permissions and avoid accidentally pulling massive result sets. 5. Watch out for query costs: Claude doesn't know your warehouse size, so phrase requests carefully to avoid expensive scans.

Works with

Claude DesktopCursor

Similar MCPs