Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
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.
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.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use this skill to integrate the Snowflake Managed MCP server with Clawdbot. It covers endpoint creation, authentication, and tool validation so Snowflake data can be accessed through MCP.
Snowflake account with ACCOUNTADMIN role Programmatic Access Token (PAT) from Snowflake Clawdbot or any MCP-compatible client
In Snowsight, go to your user menu โ My Profile Select Programmatic Access Tokens Click Create Token for your role Copy and save the token securely
Run this SQL in a Snowsight worksheet to create your MCP server: CREATE OR REPLACE MCP SERVER my_mcp_server FROM SPECIFICATION $$ tools: - name: "SQL Execution Tool" type: "SYSTEM_EXECUTE_SQL" description: "Execute SQL queries against the Snowflake database." title: "SQL Execution Tool" $$;
Verify with curl (replace placeholders): curl -X POST "https://YOUR-ORG-YOUR-ACCOUNT.snowflakecomputing.com/api/v2/databases/YOUR_DB/schemas/YOUR_SCHEMA/mcp-servers/my_mcp_server" \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --header "Authorization: Bearer YOUR-PAT-TOKEN" \ --data '{ "jsonrpc": "2.0", "id": 12345, "method": "tools/list", "params": {} }'
Create mcp.json at your project root (this is the MCP configuration Clawdbot can load for a session): { "mcpServers": { "Snowflake MCP Server": { "url": "https://YOUR-ORG-YOUR-ACCOUNT.snowflakecomputing.com/api/v2/databases/YOUR_DB/schemas/YOUR_SCHEMA/mcp-servers/my_mcp_server", "headers": { "Authorization": "Bearer YOUR-PAT-TOKEN" } } } } Start a new Clawdbot session and load mcp.json so the MCP connection is active. The Snowflake tools should appear in your session.
Start a new Clawdbot session Load mcp.json for the session Ask a question that triggers Snowflake tools (for example, a SQL query)
CREATE OR REPLACE MCP SERVER sql_mcp_server FROM SPECIFICATION $$ tools: - name: "SQL Execution Tool" type: "SYSTEM_EXECUTE_SQL" description: "Execute SQL queries against Snowflake." title: "SQL Execution" $$;
First create a Cortex Search service in Snowsight (AI & ML โ Cortex Search), then: CREATE OR REPLACE MCP SERVER search_mcp_server FROM SPECIFICATION $$ tools: - name: "Document Search" identifier: "MY_DB.MY_SCHEMA.MY_SEARCH_SERVICE" type: "CORTEX_SEARCH_SERVICE_QUERY" description: "Search and retrieve information from documents using vector search." title: "Document Search" - name: "SQL Execution Tool" type: "SYSTEM_EXECUTE_SQL" description: "Execute SQL queries." title: "SQL Execution" $$;
First upload a semantic YAML or create a Semantic View, then: CREATE OR REPLACE MCP SERVER analyst_mcp_server FROM SPECIFICATION $$ tools: - name: "Sales Analytics" identifier: "MY_DB.MY_SCHEMA.SALES_SEMANTIC_VIEW" type: "CORTEX_ANALYST_MESSAGE" description: "Query sales metrics and KPIs using natural language." title: "Sales Analytics" - name: "SQL Execution Tool" type: "SYSTEM_EXECUTE_SQL" description: "Execute SQL queries." title: "SQL Execution" $$;
CREATE OR REPLACE MCP SERVER agent_mcp_server FROM SPECIFICATION $$ tools: - name: "Documentation Agent" identifier: "MY_DB.MY_SCHEMA.MY_AGENT" type: "CORTEX_AGENT_RUN" description: "An agent that answers questions using documentation." title: "Documentation Agent" $$;
CREATE OR REPLACE MCP SERVER full_mcp_server FROM SPECIFICATION $$ tools: - name: "Analytics Semantic View" identifier: "ANALYTICS_DB.DATA.FINANCIAL_ANALYTICS" type: "CORTEX_ANALYST_MESSAGE" description: "Query financial metrics, customer data, and business KPIs." title: "Financial Analytics" - name: "Support Tickets Search" identifier: "SUPPORT_DB.DATA.TICKETS_SEARCH" type: "CORTEX_SEARCH_SERVICE_QUERY" description: "Search support tickets and customer interactions." title: "Support Search" - name: "SQL Execution Tool" type: "SYSTEM_EXECUTE_SQL" description: "Execute SQL queries against Snowflake." title: "SQL Execution" - name: "Send_Email" identifier: "MY_DB.DATA.SEND_EMAIL" type: "GENERIC" description: "Send emails to verified addresses." title: "Send Email" config: type: "procedure" warehouse: "COMPUTE_WH" input_schema: type: "object" properties: body: description: "Email body in HTML format." type: "string" recipient_email: description: "Recipient email address." type: "string" subject: description: "Email subject line." type: "string" $$;
TypePurposeSYSTEM_EXECUTE_SQLExecute arbitrary SQL queriesCORTEX_SEARCH_SERVICE_QUERYRAG over unstructured dataCORTEX_ANALYST_MESSAGENatural language queries on semantic modelsCORTEX_AGENT_RUNInvoke Cortex AgentsGENERICCustom tools (procedures/functions)
Governed by Design: Same RBAC policies apply as your data No Infrastructure: No local server deployment needed Reduced Integration: Connect any MCP-compatible client Extensible: Add custom tools via procedures/functions
SSL Error: Use hyphens instead of underscores in account name 401 Unauthorized: Verify PAT token is valid and not expired 404 Not Found: Check database, schema, and MCP server names
List available tools: curl -X POST "https://YOUR-ACCOUNT.snowflakecomputing.com/api/v2/databases/DB/schemas/SCHEMA/mcp-servers/SERVER" \ -H "Authorization: Bearer PAT" \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
PATs don't evaluate secondary roles Select a single role with all required permissions when creating Create new PAT to change role
For local deployment using the snowflake-labs-mcp package, see mcp-client-setup.md.
Snowflake MCP Server Guide Snowflake MCP Documentation GitHub: sfguide-getting-started-with-snowflake-mcp-server MCP Protocol
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.