Back to the MCP Gateway catalog

MCP Gateway · Catalog

Snowflake icon

Snowflake MCP server

Snowflake MCP is a Model Context Protocol server for Snowflake, built and hosted by Speakeasy, with OAuth and tools that let agents run queries and check or cancel running statements. Connect it through the Speakeasy MCP Gateway and agents such as Claude, Cursor, and ChatGPT get one governed URL for it, with SSO, RBAC, and a full audit trail.

Data & analytics3 toolsAuth: oauth

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.

Deploy on MCP Gateway

Tools · 3

Each tool below can be allowed or denied per team and role at the MCP Gateway, and every call is inspected and logged.

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).

Questions

What is a Snowflake MCP server?
A Snowflake MCP server exposes Snowflake to AI agents as Model Context Protocol tools. Instead of a custom integration per agent, any MCP client can connect to the server and call tools such as query or get_statement to work with Snowflake. The server in this catalog is built and hosted by Speakeasy, not published by Snowflake, and it authenticates with OAuth.
What can you do with Snowflake MCP?
Agents can run queries and check or cancel running statements, through tools such as query and get_statement. The full tool list with descriptions is on this page.
Why put Snowflake MCP behind an MCP gateway?
Connecting the Snowflake MCP server directly to each client means a separate credential per developer, no inventory of who can reach Snowflake through an agent, and no record of what agents did with it. An MCP gateway sits between every agent and the Snowflake server, so sign-in runs through your identity provider, role-based access decides which teams can call which Snowflake tools, and every call is inspected and logged in one place. The Speakeasy MCP Gateway applies those controls to Snowflake and to every other server in your catalog.
How do you connect Snowflake MCP through a gateway?
Add the Snowflake server from the Speakeasy MCP catalog and every agent reaches it through one gateway URL, next to the rest of your approved servers. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, sign-in runs through your identity provider, and role-based access controls decide which teams can use which Snowflake tools. Every prompt, response, and tool call is inspected and logged at the gateway.
How is this different from an unofficial Snowflake MCP?
Snowflake does not publish this server. It is built and hosted by Speakeasy, and this page says so instead of claiming official status. Unlike a community server you run yourself, it is delivered through the Speakeasy MCP Gateway, which adds SSO, role-based access controls, and an audit trail of every call.

AI everywhere.

Control here.

Talk to usLearn more