MCP Gateway · OpenCode
Connect Snowflake to OpenCode
OpenCode users can query Snowflake from the terminal while tracking down a data bug. Copy the Snowflake server URL from Speakeasy, add it as a remote entry in your OpenCode config, and each statement then goes through the gateway with your role's permissions.
- Category
- Data & analytics
- Tools
- 3
- Authentication
- OAuth
- OpenCode
- Terminal
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.
Set up
Add Snowflake to OpenCode in 4 steps
- 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.
- 02
Choose who can use Snowflake
Give teams the
mcp:connectscope on the Snowflake server through team access or a role. OpenCode connects to the Snowflake server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect OpenCode
Add the server to OpenCode's own mcp config block as a remote server.
Copy the server's URL from its hosted install page in Speakeasy.
Add it to the
mcpblock of your OpenCode config withtypeset toremote.Restart OpenCode and sign in when prompted.
{ "mcp": { "<server slug>": { "type": "remote", "url": "<URL from the hosted install page>" } } } - 04
Sign in and use Snowflake from OpenCode
The first time OpenCode 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 OpenCode, limited to what the person's access allows, and every call lands in the gateway's tool logs.
OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.
Use cases
What OpenCode users do with Snowflake
Trace a bad value to its source
When a customer reports a wrong number, OpenCode queries the upstream tables one step at a time until it finds the row where the value first goes wrong.
Rerun a query with different session parameters
OpenCode reruns a failing query with different session parameters on that one call, to test whether a setting explains the unexpected result.
Check a statement you left running
Come back to a submitted statement later and have OpenCode look up whether it finished, then cancel it if you no longer need the answer.
Tools
3 tools
Each Snowflake tool can be allowed or denied per team and role at the MCP Gateway before OpenCode 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 OpenCode
The gateway covers every client the same way. The rest depends on what OpenCode 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 OpenCode. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
OpenCode
The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.
Usage telemetry
OpenCode
Token and cost totals flow through the plugin, reported per turn.
Device agent
OpenCode
The device agent installs and maintains the observability package.
- OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
- Tool output is blocked at the gateway rather than in OpenCode's hooks.
Questions
Frequently asked questions
How is Snowflake usage tracked in OpenCode?
Can OpenCode call every Snowflake tool by default?
How do OpenCode users get Snowflake?
Are Snowflake calls from OpenCode logged?
Connect more