Snowflake Key Pair Auth connector for AI agents

Snowflake Key Pair Auth tools for AI agents

CALL ANY TOOL

12 tools covering get, execute, cancel.

snowflakekeyauth_get_tables

Get tables

Query INFORMATION_SCHEMA.TABLES for table metadata in a Snowflake database.

Parameters

Name

Type

Required

Description

database

string

Required

Database name

limit

integer

Optional

Maximum number of rows

role

string

Optional

Optional role

schema

string

Optional

Optional schema filter

table_name_like

string

Optional

Optional table name pattern

warehouse

string

Optional

Optional warehouse

snowflakekeyauth_create_role

Create role

snowflakekeyauth_get_columns

Get columns

snowflakekeyauth_create_user

Create user

snowflakekeyauth_get_schemata

Get schemata

snowflakekeyauth_create_table

Create table

snowflakekeyauth_get_query_status

Get query status

snowflakekeyauth_create_schema

Create schema

snowflakekeyauth_get_query_partition

Get query partition

snowflakekeyauth_create_database

Create database

snowflakekeyauth_get_table_constraints

Get table constraints

snowflakekeyauth_create_warehouse

Create warehouse

snowflakekeyauth_get_referential_constraints

Get referential constraints

snowflakekeyauth_drop_role

Drop role

snowflakekeyauth_alter_table

Alter table

snowflakekeyauth_drop_user

Drop user

snowflakekeyauth_clone_table

Clone table

snowflakekeyauth_drop_table

Drop table

snowflakekeyauth_show_grants

Show grants

snowflakekeyauth_drop_schema

Drop schema

snowflakekeyauth_alter_schema

Alter schema

snowflakekeyauth_undrop_table

Undrop table

snowflakekeyauth_drop_database

Drop database

snowflakekeyauth_execute_query

Execute query

snowflakekeyauth_undrop_schema

Undrop schema

snowflakekeyauth_alter_database

Alter database

snowflakekeyauth_clone_database

Clone database

snowflakekeyauth_drop_warehouse

Drop warehouse

snowflakekeyauth_alter_warehouse

Alter warehouse

snowflakekeyauth_show_warehouses

Show warehouses

Build your Agent

Same auth pattern across every framework.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="snowflakekeyauth")

mcp = MultiServerMCPClient({
    "snowflakekeyauth": {
        "url": "https://mcp.scalekit.com/snowflakekeyauth",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "snowflakekeyauth" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/snowflakekeyauth
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "snowflakekeyauth" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/snowflakekeyauth
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="snowflakekeyauth")
# Connect to MCP at https://mcp.scalekit.com/snowflakekeyauth
# Pass: Authorization: Bearer + token

Try these prompts

Paste any prompt into your agent to get started.

Get started

Run SHOW WAREHOUSES?

Run SHOW PRIMARY KEYS with optional scope?

Advanced

Copy the prompt

Copied

Run SHOW GRANTS in common modes (to role, to user, of role, on object)?

Copy the prompt

Copied

Run SHOW DATABASES or SHOW SCHEMAS?

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

Authorize

Your user connects

Snowflake Key Pair Auth

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Snowflake Key Pair Auth

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Snowflake Key Pair Auth

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Snowflake Key Pair Auth

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

GTM and RevOps Teams

Revenue forecast commentary

Pulls open pipeline from Salesforce and HubSpot, calculates coverage against quota, flags at-risk stages, posts commentary to Slack, and logs every snapshot to Google Sheets.

GTM and RevOps Teams

Deal intelligence agent

Pulls recent Gong calls, scores deal risk with an LLM, cross-references the record in Attio, and DMs each owner their at-risk deals in Slack. Every read is scoped to that rep's own access.

Engineering Teams

Engineering standup agent

Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.

GTM and RevOps Teams

Competitive intelligence briefing agent

Scans Gong calls for competitor mentions, matches each one to its Notion battlecard, and DMs every affected rep a single Slack digest per cycle. Every call runs as the PMM who owns the briefing, never a shared bot.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

One connector today. Ten tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Snowflake Key Pair Auth as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Snowflake Key Pair Auth bearer token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Snowflake Key Pair Auth?
Yes. Pass a tool name filter to listScopedTools so the analytics agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Snowflake Key Pair Auth.

What happens when a user revokes Snowflake Key Pair Auth access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Does query execution respect Snowflake role-based access?
Yes. Queries run under the connected key pair's Snowflake role, with row access policies and masking intact. Scalekit vaults the private key and adds per-call scope checks and audit on top.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit