To connect Claude to Snowflake with your existing permissions, add Nexatron from Claude’s Connectors Directory, or as a custom connector with the server URL https://api.nexatron.io/api/v1/mcp, then connect Snowflake to your Nexatron workspace and have users sign in with their Snowflake account or the company’s SSO. Questions then run under the user’s Snowflake default role, so role grants, row access policies, masking policies and secure views apply exactly as they do in Snowsight. Each answer carries the SQL that ran, the definition it used and the identity it ran under, so your data team can rerun it and check the number.
What you end up with
Most teams that try Claude against Snowflake start with a quick MCP server and a single warehouse credential. It works on day one and fails the first security review, because everyone who uses the connector reads what that credential can read. Finance marts, HR extracts and customer tables end up behind one role that was never designed for that audience.
The setup in this tutorial avoids that. Claude talks to Nexatron’s hosted MCP server. Nexatron talks to Snowflake under the signed-in user’s Snowflake identity, so the grants, row access policies and masking policies you already maintain decide what comes back. Nobody re-implements Snowflake security in a second place, and there is no admin view that sees more than the user would see in Snowsight.
Plan on three owners. A Snowflake administrator runs the grants and the sign-in integration, a Nexatron workspace administrator adds the connection and decides who can use it, and a Claude organization owner (on Team or Enterprise) adds the connector for the organization. In a small pilot one person often holds two of those roles.
Before you start
- A Claude plan with connectorsAnthropic’s help center lists custom connectors on Free, Pro, Max, Ultra, Team and Enterprise plans, with Free limited to one. On Team and Enterprise, Owners add connectors for the organization and members connect individually.
- A Nexatron workspace administratorA Nexatron workspace administrator adds the Snowflake connection, chooses who can use it and approves Claude for the workspace.
- A Snowflake administratorThe generated setup script needs USERADMIN and SECURITYADMIN. The sign-in integration, and the optional grant that lets setup detect policies and read query history, need ACCOUNTADMIN.
- A warehouse for NexatronQuestions run on the connection’s warehouse. A dedicated XSMALL warehouse with auto-suspend and a resource monitor keeps credit use visible and capped.
- Business roles that already make senseUsers get exactly what their Snowflake default role allows. If analysts today run as a broad shared role, fix that first, because Claude will faithfully reproduce it.
Step 1: Connect Snowflake to your Nexatron workspace
In Nexatron, open Knowledge ▸ Sources ▸ New connection and choose Snowflake. Paste your Snowflake account URL, then enter the database and warehouse. Select Generate a key for me and Nexatron fills in a setup script with your names in it. Copy it or download the .sql file for your Snowflake administrator. You can save the connection before the script has run; once it has, select Check again on the connection’s page.
The script creates a setup role that reads metadata and profiles values so Nexatron can learn the schema, with read grants on what exists and future grants on what is created later. That role never answers a question. Granting SNOWFLAKE.GOVERNANCE_VIEWER is optional and worth doing: it lets setup see which tables carry row access or masking policies, so it keeps nothing from them beyond counts, and it lets setup learn common joins from the last 14 days of query history with literals removed.
Your business roles also need USAGE on the connection’s warehouse, because users’ questions run there under their own roles. The grant below is the shape for a sales analyst role. Set a non-privileged default role for every user who will ask questions.
USE ROLE SECURITYADMIN;
GRANT USAGE ON WAREHOUSE NEXATRON_WH TO ROLE SALES_ANALYST;
GRANT USAGE ON DATABASE ANALYTICS TO ROLE SALES_ANALYST;
GRANT USAGE ON SCHEMA ANALYTICS.SALES TO ROLE SALES_ANALYST;
GRANT SELECT ON ALL TABLES IN SCHEMA ANALYTICS.SALES TO ROLE SALES_ANALYST;
GRANT SELECT ON FUTURE TABLES IN SCHEMA ANALYTICS.SALES TO ROLE SALES_ANALYST;
GRANT ROLE SALES_ANALYST TO USER JSMITH;
-- The role a session starts with, plus the other granted roles
USE ROLE USERADMIN; -- or the user's owner
ALTER USER JSMITH SET DEFAULT_ROLE = SALES_ANALYST
DEFAULT_SECONDARY_ROLES = ('ALL');Step 2: Turn on Snowflake sign-in for users
On the connection’s page, under Snowflake sign-in, pick how users authenticate to Snowflake. Snowflake OAuth sends users to Snowflake’s own sign-in page and needs only your Snowflake administrator. If the company runs Okta or Microsoft Entra ID, choose your identity provider instead: Snowflake External OAuth with the session:role-any scope, so users sign in once with the company SSO they already use. Both give a real Snowflake session for the user, and neither gives Nexatron data access of its own.
Select Show the statement. Nexatron generates the CREATE SECURITY INTEGRATION statement with the redirect URI and integration name filled in, and your Snowflake administrator runs it as ACCOUNTADMIN. Paste the client ID and secret back into Nexatron and select Save and turn on sign-in. The integration blocks ACCOUNTADMIN, SECURITYADMIN and ORGADMIN, which is the right default: nobody should be answering business questions with an administrative role.
Last, under Who can use it, choose Everyone or selected groups and people, then Save access. A new connection is available to no one until you do this, which makes it easy to start with a pilot group.
USE ROLE ACCOUNTADMIN;
CREATE SECURITY INTEGRATION IF NOT EXISTS NEXATRON_OAUTH_<CONNECTION_KEY>
TYPE = OAUTH
ENABLED = TRUE
OAUTH_CLIENT = CUSTOM
OAUTH_CLIENT_TYPE = 'CONFIDENTIAL'
OAUTH_REDIRECT_URI = '<shown in Nexatron>'
OAUTH_ENFORCE_PKCE = TRUE
OAUTH_ISSUE_REFRESH_TOKENS = TRUE
OAUTH_USE_SECONDARY_ROLES = IMPLICIT
BLOCKED_ROLES_LIST = ('ACCOUNTADMIN', 'SECURITYADMIN', 'ORGADMIN');Step 3: Add Nexatron to Claude
Nexatron is listed in Claude’s Connectors Directory as a community connector, at claude.ai/directory/nexatron. On Free, Pro, Max and Ultra (Free is limited to one custom connector), open Customize ▸ Connectors, select the + next to Connectors, find Nexatron, choose Connect and complete the Nexatron sign-in. On Team or Enterprise, an Owner opens Organization settings ▸ Connectors, selects Browse connectors, picks Nexatron and adds it to the team. Adding it there grants nobody access: members still connect from Customize ▸ Connectors.
If the directory is not available to your organization, add a custom connector with the same server. Owners use Organization settings ▸ Connectors ▸ Add ▸ Custom ▸ Web; individual plans use Customize ▸ Connectors ▸ + ▸ Add custom connector. Enter a name and the URL below, keep Claude’s recommended OAuth client option, and add it; you do not need a client ID or secret.
Claude’s labels move between releases and differ across web, desktop and mobile. Anthropic’s help pages linked below are the authority on the current menus.
https://api.nexatron.io/api/v1/mcpStep 4: Approve the workspace and sign in
If your workspace requires administrator approval, the first connection from Claude waits as pending until a Nexatron workspace administrator reviews it under Settings ▸ Integrations ▸ AI assistants (MCP) ▸ Pending approvals. Approve the intended client, then have the user reconnect. Workspace approval does not replace the user’s Nexatron role or Snowflake sign-in; it only allows the assistant into the workspace.
Claude asks for read scopes by default: mcp:read, mcp:query, openid and offline_access. That gives the analytics tools and no action tools. Access tokens last an hour and the refresh token keeps the session alive without a new sign-in, so users are not interrupted mid-analysis.
Each user then opens Knowledge ▸ Sources ▸ Your connected accounts in Nexatron and selects the Sign in with button for Snowflake. The card shows which Snowflake user they are connected as. With Snowflake OAuth, a session lasts up to 90 days before Snowflake asks again. Have two pilot users with different roles do this first; you need both for the permission test below.
How Snowflake permissions carry through to Claude
Nexatron opens the Snowflake session with the user’s DEFAULT_ROLE, and under Snowflake OAuth with their default secondary roles as well. Everything Snowflake enforces at query time then applies with no translation layer in between. Queries are read-only SELECT statements, checked before they run.
- Run the two-user testAsk the same question as a regional manager and as a finance analyst. The answers should differ exactly where their Snowflake access differs, and nowhere else.
- Test a masked column on purposeQuery a column you mask, such as salary, as a role that should see it masked. The values should come back masked, as they do in Snowsight.
| Snowflake control | What happens when the user asks in Claude |
|---|---|
| Role grants on databases, schemas and tables | Objects the role cannot read return Object does not exist or not authorized, exactly as in Snowsight. Claude cannot see around them. |
| Row access policies | The policy filters rows for the user’s role. Two users asking the same question can correctly get different totals. |
| Masking policies | Masked columns come back masked for the user’s role, exactly as in Snowsight. |
| Secure views | Read like any other view the role can select from, with the view definition hidden as Snowflake intends. |
| Administrative roles | ACCOUNTADMIN, SECURITYADMIN and ORGADMIN are blocked at sign-in, so they never answer questions. |
| Nexatron access rules | Row rules and column masking set under Settings ▸ Workspace ▸ Access apply on top. They narrow what Snowflake allows and never widen it. A question that would total, average or count a column masked by these rules is refused in words. |
Example questions to start with
Start narrow: one metric, one period, one grouping. A bounded question is easy to reconcile against a report you already trust, and it tells you quickly whether the definition Nexatron picked is the one finance uses. Semi-structured VARIANT, OBJECT and ARRAY columns are readable.
- FinanceWhat was net revenue by region last fiscal quarter, using the finance mart?
- ProductWhich customers’ monthly active users dropped more than 20% month over month?
- OperationsHow many orders shipped late last week, by warehouse and carrier?
- EngineeringWhich product events in the raw JSON stream carry an error code this month?
- PlatformWhich warehouses consumed the most credits last month, and for which workloads? This reads ACCOUNT_USAGE views only where the user’s role can.
- GrowthWhat is the 90-day retention of customers acquired in each quarter of last year?
Check the definition, source and query behind an answer
A number in a chat window is only useful if someone can check it. Claude shows each tool call in the conversation, and Nexatron’s ask tool returns the rows, the generated SQL and lineage alongside the answer. In the Nexatron app the same answer shows How this was answered, with Access naming whose permissions applied, Why you can see this, a trust label such as Approved or Interpreted for where the definition came from, and a Not included list for anything left out.
For a named metric, ask Claude to call list_metrics to see the definitions available to you, and explain_metric to read the formula, filters, table and the columns it can be grouped by. Then use query_metric to run that definition directly. If a question used an interpreted definition, that is your cue to have the metric owner approve one before the number goes in a deck.
Finally, copy the SQL into Snowsight and run it as the same user. Because the query ran in the user’s own Snowflake session, it also appears in Query History under that user, on the connection’s warehouse. Matching totals there is the strongest check you can do, and it is the one your auditors will understand.
Troubleshooting
Two rules save a lot of time. Never switch to an administrator account to make a failing question work, because it hides the fault and can put data in a conversation that should never have seen it. And reconnect with the same account after an authorization error, so you are testing the access you actually intend to ship.
| Symptom | Likely cause and fix |
|---|---|
| Object does not exist or not authorized | The user’s role lacks USAGE on the database, schema or warehouse, or SELECT on the object. Check the user’s role, not the setup role. For new tables, a schema-level future grant overrides the database-level one. |
| Sign-in or question fails with a role error | The user’s default role is blocked (ACCOUNTADMIN, SECURITYADMIN, ORGADMIN) or not granted to them. Set a non-privileged default role. |
| Incoming request with IP/Token ... is not allowed | An account or user network policy does not include Nexatron’s egress IP addresses, which the connection page shows. User sessions connect from Nexatron’s servers too. |
| External OAuth: user not found | The mapping claim does not equal the Snowflake LOGIN_NAME, or the issuer or audience does not match the token exactly. |
| Claude shows the connection as pending | A Nexatron workspace administrator needs to approve it under Pending approvals. Reconnect afterwards with the same account. |
| Tools missing in Claude | Check that Nexatron is toggled on for the conversation from the + menu and that an Owner has not blocked the tools. |
| Empty result | An empty result is not proof that no rows exist. Check the user’s Snowflake sign-in and role before widening anything. |
FAQ
- Is Nexatron a Snowflake MCP server?Nexatron is a hosted MCP server that answers over Snowflake and the other systems your workspace connects, with approved metric definitions and the user’s Snowflake permissions. Snowflake also offers a managed MCP server that exposes Cortex Agents, Cortex Analyst, Cortex Search and SQL as tools; Nexatron adds definitions, cross-source questions and one endpoint for every assistant.
- Does Claude ever see a Snowflake password or key?No. Claude authorizes to Nexatron with OAuth, and users authorize Snowflake through Snowflake OAuth or the company SSO. Source credentials and MCP tokens are separate.
- Do we need SSO?SSO is optional. Snowflake OAuth works with Snowflake’s own sign-in page. If you run Okta or Microsoft Entra ID, External OAuth lets users sign in with the company SSO they already use.
- Can Claude write to Snowflake?Questions are read-only SELECT statements. Claude’s default connection asks for read scopes only, and action tools are a separate set that a workspace administrator controls.
- What does it cost?Snowflake bills the warehouse credits your questions use, which is why a dedicated warehouse with a resource monitor helps. For Nexatron pricing, contact sales.
- Does the same setup work in ChatGPT and Copilot?Yes. ChatGPT and Microsoft 365 Copilot use the same server URL, and the Snowflake permissions apply in the same way whichever assistant asks.
Claude is a trademark of Anthropic, PBC.
Bring three business questions
Explore your sources, definitions, and review criteria with our team. Please keep credentials and sensitive records out of the inquiry.