MCP Gateway · Cursor
Connect Snowflake to Cursor
Cursor can run the SQL you're writing against Snowflake and show the output beside the code. The Speakeasy MCP Gateway gives every developer one URL for Snowflake, checks each call against their role before it runs, and records who executed each statement.
- Category
- Data & analytics
- Tools
- 3
- Authentication
- OAuth
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Snowflake MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Snowflake call inspected and logged.
Set up
Add Snowflake to Cursor in 4 steps
- 01
Add Snowflake from the catalog
An admin finds Snowflake in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Snowflake uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Snowflake
Give teams the
mcp:connectscope on the Snowflake server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Snowflake to their gateway on the next call, and removing it takes it away. - 03
Connect Cursor
Add the gateway to Cursor in one click from the Organization Gateway page.
On the Organization Gateway page in Speakeasy, choose Cursor under Install.
Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.
- 04
Sign in and use Snowflake from Cursor
The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Snowflake needs its own OAuth grant, so each person connects it once. Until they do, Snowflake calls fail while the rest of the gateway keeps working.
From then on, Snowflake's tools appear in Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.
For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.
Use cases
What Cursor users do with Snowflake
Try a query while building an endpoint
Write the SQL for a reporting endpoint in the editor and have Cursor run it with a server-side timeout, so you see real output before wiring it into the API.
Cancel a query started by mistake
If you ran an expensive query against the wrong warehouse, Cursor cancels the running statement right away so it doesn't keep going in the background.
Build test fixtures from sample rows
Cursor queries a small sample from a table and turns the rows into fixtures for the unit tests you're writing, so tests use realistic shapes of data.
Tools
3 tools
Each Snowflake tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.
cancel_statement
Cancel a running Snowflake statement by handle.
get_statement
Fetch the status and results of a previously submitted Snowflake statement by handle. Use this after submitting a query with async=true, or to page through large result sets via the partition parameter.
query
Run a SQL statement against Snowflake. Supports overriding warehouse/database/schema/role per call, session parameters, server-side timeout, and async submission (returns a statementHandle to fetch later via get_statement).
Control
What Speakeasy can see and stop in Cursor
The gateway covers every client the same way. The rest depends on what Cursor exposes to Speakeasy.
Tool logs
Gateway
Every Snowflake call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Snowflake tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Snowflake can reject a tool request before it reaches the server, or withhold a result from Cursor. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Cursor
Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.
User attribution
Cursor
Every Cursor hook event carries the user's email.
Budgets
Cursor
Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.
Device agent and MDM
Cursor
The device agent installs the marketplace and plugins and reapplies them every minute.
- Cursor Cloud agents need a checked-in
.cursor/hooks.json. Session and MCP-specific hooks don't run there. - After a plugin update, members run Developer: Reload Window.
Questions
Frequently asked questions
Do Speakeasy's checks on Snowflake calls run in Cursor Cloud agents?
Can Speakeasy cap what Cursor spends?
How do Cursor users get Snowflake?
Are Snowflake calls from Cursor logged?
Connect more