Skip to main content
Back to the Snowflake MCP server

MCP Gateway · Claude

Snowflake icon

Connect Snowflake to Claude

Claude can answer business questions by running SQL against Snowflake and explaining the result in plain language. Through the Speakeasy MCP Gateway, each person connects once from Customize > Connectors, sees only the Snowflake tools their role can reach, and never handles a database credential.

Category
Data & analytics
Tools
3
Authentication
OAuth
Claude
Web, desktop and mobile

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

Set up

Add Snowflake to Claude in 4 steps

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

  2. 02

    Choose who can use Snowflake

    Give teams the mcp:connect scope 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.

  3. 03

    Connect Claude

    Add the gateway URL as a custom connector, then connect it from Customize > Connectors.

    On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.

    Each person opens Customize > Connectors and clicks Connect to sign in.

    On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.

  4. 04

    Sign in and use Snowflake from Claude

    The first time Claude 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 Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.

No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.

Use cases

What Claude users do with Snowflake

Answer a quick numbers question

Ask how many orders shipped last month by region, and Claude writes and runs the query, then explains the result in a sentence or a small table.

query

Explain a metric before a meeting

Claude queries the figures behind a metric that moved, compares them with the prior period and writes a short note you can paste into the agenda.

query

Pick up results from a slow question

For a large question, Claude submits the query to run asynchronously and collects the answer once Snowflake is done, instead of timing out.

queryget_statement

Tools

3 tools

Each Snowflake tool can be allowed or denied per team and role at the MCP Gateway before Claude 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 Claude

The gateway covers every client the same way. The rest depends on what Claude 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 Claude. MCP-scoped policies are enabled per organization.

Anthropic inference hooks

Claude

On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.

Conversation import

Claude

Claude conversations can be imported through Anthropic's Compliance API for review after the fact.

  • Custom connectors need a Claude plan that supports them.
  • Budgets don't cover Claude web and desktop usage.

Questions

Frequently asked questions

Can Speakeasy block a Snowflake prompt in Claude before it runs?
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Do budgets apply to Snowflake use in Claude?
No. Budgets don't cover Claude web and desktop usage. Access is limited by role instead, since each person only sees the servers their role can reach.
How do Claude users get Snowflake?
An admin adds Snowflake from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway URL as a custom connector, then connect it from Customize > Connectors. Each person then sees only the Snowflake tools their access allows.
Are Snowflake calls from Claude logged?
Yes. Snowflake calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Snowflake in other clients

AI everywhere.

Control here.