pggm-mcp-snowflake-server

An MCP server (pggm-mcp-snowflake-server) that connects an agent to Snowflake, exposing Snowflake-related capabilities as MCP tools so an AI agent can query and/or manage data in Snowflake via the MCP protocol.

Evaluated Apr 04, 2026 (27d ago)
Homepage ↗ Infrastructure mcp snowflake database data-warehouse agents sql
⚙ Agent Friendliness
41
/ 100
Can an agent use this?
🔒 Security
41
/ 100
Is it safe for agents?
⚡ Reliability
28
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
35
Error Messages
0
Auth Simplicity
50
Rate Limits
20

🔒 Security

TLS Enforcement
60
Auth Strength
45
Scope Granularity
20
Dep. Hygiene
45
Secret Handling
35

Security posture depends on how the server accepts/stores Snowflake credentials and how it constrains operations (e.g., read-only vs write, query allowlists, row-level security). TLS is likely but not confirmed from the provided content. Scope granularity is unknown and should be considered weak until verified (e.g., a single broad Snowflake account/role).

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
30
Error Recovery
40
AF Security Reliability

Use Cases

  • Agent-assisted Snowflake querying and data retrieval (SQL generation + execution)
  • Snowflake schema exploration for agent workflows
  • Automating analytics/ETL preparation steps via agent-invoked Snowflake actions

Not For

  • Direct production database administration tasks without guardrails
  • Use cases requiring strong, explicit tenant isolation guarantees unless the package enforces it
  • Environments where outbound network access to Snowflake is not permitted

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: Snowflake credentials (typically via username/password, key-pair, or OAuth/SSO depending on deployment)
OAuth: No Scopes: No

Auth and authorization mechanisms are not provided in the supplied prompt content. For MCP-to-Snowflake servers, auth is typically implemented by accepting Snowflake connection parameters (or a secrets reference) and may require careful handling to avoid over-broad access.

Pricing

Free tier: No
Requires CC: No

No pricing information provided.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • SQL generation mistakes can lead to runtime errors or expensive queries; ensure the server/agent adds safeguards (limits, allowlists)
  • Agents may not automatically respect Snowflake resource/warehouse settings; consider guardrails in the tool layer
  • If connection handling is stateless, repeated calls can increase connection overhead; cache/keep-alive may be needed (depends on implementation)

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for pggm-mcp-snowflake-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered