Let your team use Claude

Draft. This needs flurry’s Snowflake app, which is not released yet. The steps will be checked against the real app before it ships.

Claude (desktop, web and Cowork) connects to flurry through Snowflake’s own sign-in. You set this up once; each person then adds flurry in Claude with three clicks.

Turning this on means what a person asks Claude, and the results their agent reads, go to Anthropic under your company’s Claude agreement. See what leaves your account.

Create the sign-in. As ACCOUNTADMIN, run:

CREATE SECURITY INTEGRATION FLURRY_CLAUDE
  TYPE = OAUTH
  OAUTH_CLIENT = CUSTOM
  OAUTH_CLIENT_TYPE = 'PUBLIC'
  OAUTH_REDIRECT_URI = 'https://claude.ai/api/mcp/auth_callback'
  OAUTH_ENFORCE_PKCE = TRUE
  OAUTH_ENABLE_ROLE_SELECTION = TRUE
  OAUTH_USE_SECONDARY_ROLES = IMPLICIT
  ENABLED = TRUE;

Copy the client ID. Run SELECT SYSTEM$SHOW_OAUTH_CLIENT_SECRETS('FLURRY_CLAUDE'); and copy OAUTH_CLIENT_ID. Leave the secret alone; Claude doesn’t need it.
Turn it on in flurry. In flurry, open Admin › Access, choose Manage next to Claude, and paste the client ID.
Tell your team. Each person clicks Connect AI in flurry and picks the Claude tab. It shows the address to paste into Claude’s Settings › Connectors › Add custom connector, and the client ID to paste under Advanced.

Two rules people trip on

People who use the connector must not hold an admin role, not even as a secondary role. Snowflake refuses the sign-in for them.
Each person signs in to Snowflake once in a browser before their first chat.

Didn’t work?

See troubleshooting.