Skip to main content
Back to the Snowflake MCP server

MCP Gateway · Claude Cowork

Snowflake icon

Connect Snowflake to Claude Cowork

Cowork can take on longer data tasks in Snowflake, such as running a set of queries, checking each result and writing up what they show. Snowflake reaches Cowork through a plugin synced from your organization's marketplace, and Speakeasy checks each prompt before the step runs.

Category
Data & analytics
Tools
3
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

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 Cowork 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. Claude Cowork connects to the Snowflake server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Snowflake from Claude Cowork

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

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Snowflake

Build a monthly metrics pack

Cowork runs each query behind your monthly metrics, waits for the slower ones to finish, and assembles the results into one report with a note on each change.

queryget_statement

Reconcile two sources of a figure

Give Cowork two tables that should agree, and it queries both, narrows down the rows that differ and explains each gap in a short write-up.

query

Run a batch of data checks

Cowork works through a list of data-quality checks, sets a server-side timeout on each, cancels any statement that stalls, and reports which checks passed.

querycancel_statement

Tools

3 tools

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

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

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Does the Snowflake plugin update in Cowork automatically?
Cowork reads the synced repository, so a new session picks up plugin changes. Each server's overview page in Speakeasy shows which plugin it is published to.
Can personal Claude accounts use Snowflake in Cowork?
No. Personal Claude accounts can't be governed in Cowork. The Claude-side plugin setup always applies, since neither the device agent nor MDM reaches Cowork.
How do Claude Cowork users get Snowflake?
An admin adds Snowflake from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Snowflake tools their access allows.
Are Snowflake calls from Claude Cowork 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.