Skip to main content

Snowflake

A Snowflake-managed MCP server is an object you create in a database and schema. Clients call https://{account}/api/v2/databases/{database}/schemas/{schema}/mcp-servers/{server}. Snowflake does not support dynamic client registration. An admin creates an OAuth security integration and pastes its client ID and secret into Willow. One integration can serve every user and every MCP server in the account. Each person still signs in with their own Snowflake user. It is the Snowflake card with the Official badge. Willow also has a built-in Snowflake connector.

The session role is the user's DEFAULT_ROLE, not a role picked in Willow. Set DEFAULT_ROLE to the MCP access role, and set a DEFAULT_WAREHOUSE that role can use.

Set up Snowflake​

  1. Create the MCP server with CREATE MCP SERVER in the database and schema. Tool names in one server must be unique. Hostnames in the account URL should use hyphens, not underscores.
  2. Create a confidential OAuth integration. Set OAUTH_REDIRECT_URI to the URI from Willow's setup step.
CREATE SECURITY INTEGRATION IF NOT EXISTS WILLOW_MCP
TYPE = OAUTH
OAUTH_CLIENT = CUSTOM
ENABLED = TRUE
OAUTH_CLIENT_TYPE = 'CONFIDENTIAL'
OAUTH_REDIRECT_URI = '<redirect URI from Willow>'
OAUTH_USE_SECONDARY_ROLES = NONE
ALLOWED_ROLES_LIST = ('MCP_ACCESS_ROLE');
  1. Read the client id and secret:
SELECT SYSTEM$SHOW_OAUTH_CLIENT_SECRETS('WILLOW_MCP');

Keep OAUTH_USE_SECONDARY_ROLES = NONE. A client may display secondary roles as ALL. Snowflake enforces the integration setting.

If the account uses PrivateLink and Willow calls from the public internet, give Willow the public MCP URL and set USE_PRIVATELINK_FOR_AUTHORIZATION_ENDPOINT = TRUE on the integration.

Set up Willow​

  1. Go to MCP Servers → + Add MCP server, open the Snowflake card with the Official badge, and click + Use.
  2. Enter the account host, database, schema, and server name.
  3. Keep OAuth sign-in. Paste the client ID and secret from SYSTEM$SHOW_OAUTH_CLIENT_SECRETS.
  4. Click Check connection and sign in as a user whose default role is in ALLOWED_ROLES_LIST. Assign groups and Publish.

Troubleshooting​

Sign-in works and the session fails to start​

Cause: The user has no DEFAULT_WAREHOUSE, or DEFAULT_ROLE is not in ALLOWED_ROLES_LIST.

Solution: ALTER USER ... SET DEFAULT_ROLE = MCP_ACCESS_ROLE DEFAULT_WAREHOUSE = <warehouse>.

Additional Resources​