Bring Sql Query
to Cursor
Learn how to connect Snowflake to Cursor and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Snowflake MCP Server?
Connect your Snowflake account to any AI agent to automate your data cloud operations and analytical workflows. Snowflake provides a premier platform for data warehousing and analysis, and this integration allows you to execute SQL statements, browse database schemas, and monitor session contexts through natural conversation.
What you can do
- SQL Query Orchestration — Execute any SQL statement programmatically and retrieve real-time data results for immediate analysis.
- Database & Schema Oversight — List and search through databases, schemas, and tables to maintain a clear overview of your data architecture directly from the AI interface.
- Warehouse & Resource Control — Access and monitor available warehouses and user roles to ensure your analytical environment is properly configured.
- Metadata Intelligence — Describe table structures and retrieve session context metadata via natural language commands to facilitate data exploration.
- Operational Monitoring — Track statement execution status and cancel long-running queries to ensure your data cloud resources are used efficiently.
How it works
1. Subscribe to this server
2. Enter your Snowflake Account Identifier and Token (JWT or OAuth2)
3. Start managing your data cloud from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Data Analysts — quickly retrieve query results and explore table schemas without switching between SQL editors.
- BI Engineers — automate the retrieval of database metadata and monitor warehouse usage via natural conversation.
- Data Scientists — streamline the exploration of large datasets and track session contexts directly within the chat.
Built-in capabilities (11)
Cancel a running SQL statement
Get table schema details
Returns the first partition of results or a handle for long-running queries. Execute a SQL statement in Snowflake
Get current session context
Check the status of a SQL statement
List all accessible databases
List security roles
List schemas in a database
List tables in a schema or database
List Snowflake users
List compute warehouses
Why Cursor?
Cursor's Agent mode turns Snowflake into an in-editor superpower. Ask Cursor to generate code using live data from Snowflake and it fetches, processes, and writes. all in a single agentic loop. 11 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Snowflake in Cursor
Snowflake and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Snowflake to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Snowflake in Cursor
The Snowflake MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Snowflake for Cursor
Every tool call from Cursor to the Snowflake MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Snowflake Account Identifier?
Your Account Identifier is the part of your Snowflake URL before '.snowflakecomputing.com'. It typically looks like xy12345.us-east-2.aws.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.