Skip to main content
Back to the Snowflake MCP server

MCP Gateway · Codex

Snowflake icon

Connect Snowflake to Codex

Codex can run SQL against Snowflake to test the assumptions in a data change before it ships. Engineering teams reach Snowflake through the Speakeasy MCP Gateway, where each tool is allowed or denied per role and every call lands in one audit log tied to a named engineer.

Category
Data & analytics
Tools
3
Authentication
OAuth
Codex
CLI and ChatGPT desktop app

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

    Add the gateway as an MCP server, then log in.

    Run the first command with your organization gateway URL.

    Run the second command to sign in.

    codex mcp add 'speakeasy' \
      --url 'https://<organization host>/mcp/gateway/<organization slug>'
    codex mcp login 'speakeasy'
  4. 04

    Sign in and use Snowflake from Codex

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

To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.

Use cases

What Codex users do with Snowflake

Compare row counts after a pipeline change

Codex runs the same count against the old and new tables and reports where the numbers differ, so a broken join shows up before the pull request goes to review.

query

Page through a large result set

When a query returns more rows than fit in one response, Codex pages through the remaining results by handle and summarizes what it found across all of them.

get_statement

Test against a staging schema

Codex overrides the database, schema and role on a single call to run a check in staging, without touching the defaults your other queries use.

query

Tools

3 tools

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

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

Prompt and tool-call blocking

Codex

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

User attribution

Codex

An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.

Budgets

Codex

Spend limits can block Codex traffic once a budget is reached.

Device agent and MDM

Codex

The device agent keeps Codex's configuration in sync on managed laptops.

  • Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
  • The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.

Questions

Frequently asked questions

How does a team get Snowflake in Codex without each engineer running the command?
A ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.
Is Codex telemetry for Snowflake calls on by default?
No. An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy, and export is off by default.
How do Codex users get Snowflake?
An admin adds Snowflake from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway as an MCP server, then log in. Each person then sees only the Snowflake tools their access allows.
Are Snowflake calls from Codex 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.