# Your Snowflake data. One question away.

Source: https://corespeed.io/integrations/snowflake

Connect Snowflake to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent lists databases, schemas and tables, describes a table's columns, and runs SQL through Snowflake's SQL API. It uses a programmatic access token you create, so it sees only what that token's role can. Any statement is a call your approval policy can hold.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Snowflake after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up

## Ask in plain words. Read the SQL it ran

Your agent finds the table, checks the columns, and runs one SELECT. You see the result and the statement behind it.

You ask your agent: "In Snowflake, find the orders and returns tables in SALES. Check their columns, then show the October return rate by region, with the SQL you ran."

It calls CoreSpeed:

- `snowflake__list_tables`: ok, 512 ms
- `snowflake__describe_table`: ok, 344 ms
- `snowflake__execute_query`: ok, 2210 ms

It reads from: Snowflake.

### Return rate: October, by region.

Returns were highest in the West. The statement ran as one SELECT under the token's role.

**By region**

- West: 7.8% of orders returned.
- East: 5.1%.
- Central: 4.6%.
- South: 4.2%.

**Query**

- ORDERS joined to RETURNS on ORDER_ID, October 2026.

_Illustrative example · Fictional data · One SELECT, no data changed_

All connectors: https://corespeed.io/docs/connectors

## Know the schema before the query runs

Requests you can make once Snowflake is connected. The data is fictional.

### Find where the data lives

SALES · PUBLIC · Schemas and tables

- Database: SALES
- Schema: PUBLIC
- Visible to the token's role

### Check the columns

ORDERS · columns · Column types

- Columns: 24
- Key: ORDER_ID
- Read before any query

### Hold a change for a person

A delete waits · Approvals

- Statement: DELETE on RETURNS
- Policy: Ask before changing data
- Ask

Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md)

## Keep your agent. Bring your work

One CoreSpeed account, across compatible agents.

1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in.
2. **Connect Snowflake**: Authorize the account and the content you need.
3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer.

Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### How does CoreSpeed sign in to Snowflake?

With your account URL and a programmatic access token you create in Snowflake. Access follows the token's role, so give it the least privilege it needs.

### Can the agent change data in Snowflake?

Only if the token's role allows it. Both SQL tools can have effects, even a SELECT that calls a procedure, so your approval policy can hold either one.

### Who pays for the warehouse time?

Your Snowflake account, as for any client. Statements run on your warehouses at your Snowflake rates.

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

### Does this work without connecting an account?

No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors

Every tool and price: https://corespeed.io/catalog/snowflake

## Related pages

- [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents.
- [BigQuery for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/bigquery): Ask BigQuery a question from your agent. It finds the table, reads the schema, and runs the SQL, and you see the query it ran.
- [Supabase for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/supabase): Let your agent work in your Supabase project: tables, SQL, migrations, logs and advisors, through your own Supabase account.

## Sources

- Connectors: https://corespeed.io/docs/connectors
- Snowflake SQL API: submitting requests: https://docs.snowflake.com/en/developer-guide/sql-api/submitting-requests
- Programmatic access tokens: https://docs.snowflake.com/en/user-guide/programmatic-access-tokens

Reviewed 2026-11-10.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)