Skip to main content
Back to the Snowflake MCP server

MCP Gateway · Claude Code

Snowflake icon

Connect Snowflake to Claude Code

Claude Code can query Snowflake from the terminal while you write the code that depends on the data. Through the Speakeasy MCP Gateway, every developer reaches Snowflake at the same governed URL, calls only the tools their role allows, and leaves an audit entry for each statement Claude Code runs.

Category
Data & analytics
Tools
3
Authentication
OAuth
Claude Code
CLI

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 Code 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 Code

    Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.

    Run the command below with your organization gateway URL.

    Open /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use Snowflake from Claude Code

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

To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.

Use cases

What Claude Code users do with Snowflake

Check a table before a migration

Have Claude Code run a SQL statement against the schema you're about to change, overriding the warehouse and role for that one call, so the migration matches the real columns.

query

Run a heavy check in the background

Submit a slow count query asynchronously and keep coding. When it finishes, Claude Code fetches the status and rows using the statement handle and tells you what changed.

queryget_statement

Stop a runaway query

If a statement Claude Code started is taking far longer than expected, cancel it using its handle instead of waiting for the server-side timeout to end it.

cancel_statement

Tools

3 tools

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

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

Prompt and tool-call blocking

Claude Code

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.

User attribution

Claude Code

Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.

Budgets

Claude Code

Spend limits can block Claude Code traffic once a budget is reached.

Device agent and MDM

Claude Code

The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.

Anthropic inference hooks

Claude Code

On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).

  • Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
  • Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.

Questions

Frequently asked questions

Can I stop Claude Code from running certain Snowflake statements?
Agent hooks send each tool call to Speakeasy, which allows or denies it before Claude Code runs it. At the gateway, an admin also decides which of the 3 Snowflake tools each team can call.
Does the Snowflake setup work for Claude Code on the web?
Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
How do Claude Code users get Snowflake?
An admin adds Snowflake from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the Snowflake tools their access allows.
Are Snowflake calls from Claude Code 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.