Snowflake MCP Connection

Connect to the Snowflake Managed MCP server with Clawdbot or other MCP clients. Use when wiring Snowflake MCP endpoints, validating connectivity, or configuring Cortex AI services.

This skill is documentation and SQL examples for configuring Snowflake MCP servers and connecting Clawdbot — it does what it says. Before using: (1) do not paste PATs or passwords into public repos or project files (mcp.json, connections.toml); use a secrets manager or environment-specific secure storage; (2) avoid passing plaintext passwords on command lines where possible (use key auth or protected connection files); (3) grant the smallest Snowflake role/privileges necessary (avoid using ACCOUNTADMIN unless required); (4) when running a local MCP client (snowflake-labs-mcp), install software only from trusted sources and review the project; and (5) review sql_statement_permissions in the provided template to ensure DDL/DML/administrative statements are appropriately restricted. If you need the agent to act autonomously with credentials present, be aware that giving the agent access to stored tokens increases risk — prefer manual steps or tightly-scoped tokens.

Type: OpenClaw Skill Name: snowflake-mcp Version: 2.0.2 The skill bundle provides comprehensive instructions and configuration examples for integrating OpenClaw with Snowflake's Managed Context Protocol (MCP). While it enables powerful capabilities such as arbitrary SQL execution via the `SYSTEM_EXECUTE_SQL` tool and local command execution for a local MCP server (`uvx snowflake-labs-mcp`), these are explicitly documented as part of the intended functionality and integration methods. There is no evidence of intentional harmful behavior, data exfiltration, prompt injection against the agent, or obfuscation. The `configuration-template.yaml` even demonstrates good security practice by defaulting DDL/DML permissions to `False` for the local server.