Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Snowflake to Claude Code

Let Claude run queries and make scoped writes against your Snowflake data. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Snowflake to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Snowflake, you add a Snowflake MCP server: a small hosted service that exposes Snowflake's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Snowflake account. No API keys pasted into config files.

claude mcp add --transport http snowflake https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Snowflake once connected?

Full read-write Snowflake access lets Claude run parameterized queries, insert and update rows, load staged data, and apply schema or transformation changes against a database you control. The data exploration, cleanup, and routine modeling work that used to mean hand-writing SQL in a worksheet happens in conversation, with every write reviewed before it runs.

  • Insert or update rows in a specified table using parameterized statements
  • Run a query to explore a table, then propose the change it implies
  • Load data from a stage into a target table after you approve it
  • Apply a schema change such as adding a column or creating a view
  • Run a transformation or backfill, showing affected row counts first
  • Inspect databases, schemas, and warehouse usage to plan a change

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Snowflake access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Snowflake API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Snowflake changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Snowflake connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Snowflake connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Snowflake account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Snowflake's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Snowflake?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Snowflake account it signs in with. Revoking access is one click in Snowflake.

More on the Snowflake connector

Snowflake connector for claude.aiAirtable + Claude CodePostgreSQL + Claude CodeMySQL + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us