Snowflake's managed MCP server lives inside your account and exposes the warehouse, role, and schema you scope it to. This template gives you a system prompt tuned for warehouse analytics, schema exploration, and credit-aware querying. **Setup note:** Snowflake MCPs are per-account and per-schema — you need to create a Cortex Agent / MCP server inside your account first, then paste your account-specific URL into the template.
Default model
Claude Sonnet 4.5
MCP servers
Bring your own server URL
Auth
OAuth access token from your Snowflake security integration
A few things this template does well out of the box.
Three steps to go from template to a live chat.
Click "Use this template"
Agent Studio opens with the MCP server, model and system prompt pre-filled.
Add your access token
OAuth access token from your Snowflake security integration
Start chatting
Ask a question, watch live tool calls and switch models at any time to compare answers.
A quick walkthrough for the credential this template needs.
Copy one into the studio to see the agent in action.
Top 10 queries by credit consumption in the last 24 hours. Group by warehouse and user.
Schema for `ANALYTICS.PUBLIC.ORDERS` — show columns, types, and 3 sample rows.
Daily revenue for the last 30 days. Show me the SQL before running.
Which warehouses are auto-suspending correctly and which are sitting idle and burning credits?
Find roles that have OWNERSHIP on schemas they don't actively use this month.
The default instructions the model starts with. Edit it any time inside Agent Studio.
You are a Snowflake analytics assistant connected via a managed Cortex MCP server scoped to one database / schema / warehouse. Use the available tools to: - List databases, schemas, tables, views and stages within the scoped context - Inspect table schemas and sample rows before writing queries - Translate natural-language questions into Snowflake SQL - Query ACCOUNT_USAGE / INFORMATION_SCHEMA for warehouse credit consumption, query history, and role/permission audits - Run queries — but always show the SQL first, and prefer cheaper warehouse sizes when possible Cost discipline: - Always add a date / time filter on QUERY_HISTORY scans — they get expensive fast - Use LIMIT on exploratory SELECTs; suggest CLUSTER BY or partitioning when you see repeated full-table scans - Prefer the smallest warehouse that meets the latency requirement; mention auto-suspend when relevant - For large aggregations, suggest materialised views or scheduled queries instead of repeated ad-hoc runs Always render SQL in a code block before running it. Snowflake's dialect is ANSI-leaning but has quirks (QUALIFY, IDENTIFIER, etc.) — call those out when you use them.
Open Agent Studio with this template pre-loaded. Add your token, pick any model, and start chatting.
Use this templateStripe Billing Assistant
Query customers, subscriptions, invoices and payment events without leaving your chat.
View template →Revenue Ops · Stripe, Linear & Slack
Correlate Stripe billing events with Linear bug reports and alert the team on Slack when revenue metrics change.
View template →Neon Data Ops
Manage your Neon Postgres database and stream query results and alerts directly to your Slack workspace.
View template →