Connect Snowflake to Claude Code

Browse databases, schemas and tables, and run SQL through the Snowflake SQL API. Add Toolspoke to Claude Code once and it can use 8 Snowflake actions. Your Snowflake credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Snowflake and connect it

    Add Snowflake to a project in your Toolspoke workspace.

    Programmatic access token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    Account identifier
    The organization-account name from Snowsight → Account details, written with a hyphen. It becomes the host: https://myorg-myaccount.snowflakecomputing.com.
    Programmatic access token
    Snowsight → your user → Programmatic access tokens, or ALTER USER <name> ADD PROGRAMMATIC ACCESS TOKEN <token_name>. The secret is shown once. It inherits the role you bind it to, bind it to a read-only role unless this install must write.
  3. Choose what Claude Code may do

    All 8 actions start on. Switch off any of the 2 actions that change something in Snowflake, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Snowflake actions that only read, so they are safe to try first.

  • List the databases the token's role can see, with owner, comment, retention time and creation date
  • List the schemas inside one database
  • List the tables in one schema, with row counts and bytes where Snowflake tracks them
  • List the virtual warehouses the token's role can use, with size, state and auto-suspend settings

What Claude Code can do in Snowflake

6 actions read, one writes and one deletes or permanently changes something.

Reads

  • List databases

    List the databases the token's role can see, with owner, comment, retention time and creation date. Call this first, every schema, table and describe operation needs a database name, and this is the cheapest call in the connector: it runs no warehouse and costs no credits.

  • List schemas

    List the schemas inside one database. Use it between list_databases and list_tables to find where the tables you want actually live, a large Snowflake account puts raw, staging and modelled data in different schemas of the same database. Costs no credits.

  • List tables

    List the tables in one schema, with row counts and bytes where Snowflake tracks them. Use it to find a table name before describe_table, and to judge how large a table is before writing a query against it. Costs no credits.

  • Describe table

    Describe one table: every column with its type, nullability, default and comment, plus the table's clustering key and comment. Call this before writing any statement against a table you have not seen, it is what stops a query failing on a column that does not exist, and it costs no credits, unlike discovering the same thing by running a SELECT.

  • List warehouses

    List the virtual warehouses the token's role can use, with size, state and auto-suspend settings. Call this when submit_statement reports no warehouse, or to pick the smallest warehouse that can answer a question, the warehouse is what a query costs credits on. Costs no credits itself.

  • Get statement

    Fetch the status and results of a statement already submitted, by its statementHandle. A 202 means it is still running, poll again; a 200 carries `resultSetMetaData` and `data`. This is how you finish an async submit_statement, and how you retrieve a further page of a large result set by passing `partition`.

Writes

  • Submit statement

    Run one SQL statement on a warehouse and return its result set. Classified as a write because Snowflake's SQL API has no read-only mode: the same endpoint serves SELECT, INSERT and DDL, and nothing here can prove which one a caller sent. Bind the access token to a read-only role if this install should only ever read. Always put an explicit LIMIT on a SELECT, the rows come back verbatim and a wide table will exhaust your context. Use the metadata reads (list_tables, describe_table) for schema questions instead; they cost no credits, and this does. If the response has no `data`, the statement is still running: take `statementHandle` and poll get_statement.

Deletes or permanently changes

  • Cancel statement

    Cancel a statement that is still running, by its statementHandle. Destructive because it aborts work in progress: a long INSERT or MERGE stops part-way and Snowflake rolls it back, and the credits already burned on the warehouse are not returned. Use it on a runaway query found through get_statement, not as a routine cleanup step.

Snowflake in Claude Code: questions

Does Claude Code see my Snowflake credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Snowflake?

Yes. Each of the 8 actions can be switched off for a project. Turn off the 2 that change something and Claude Code can only read.

Will 8 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Snowflake action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Snowflake call does not run in a sandbox, so it bills nothing.

Try Snowflake in Claude Code

Free to start, and tool calls cost nothing on any plan.