Snowflake-managed MCP
Snowflake (official)
Streamable HTTPTool names not enumerated3
About Snowflake-managed MCP
Snowflake-managed MCP server exposes configured Cortex Agent, Cortex Search, Cortex Analyst, SQL execution, coding agent, and custom UDF/stored-procedure tools with Snowflake OAuth and role-based controls.
What you can use it for
- Expose governed Cortex Analyst and Cortex Search capabilities to MCP clients
- Expose a configured Cortex Agent or custom Snowflake tools
- Run supported Snowflake SQL tools through a role-governed MCP endpoint
Connection and setup
- Hosting
- Remote, Snowflake-managed per account/database/schema MCP server object
- Transport
- Streamable HTTP
- Endpoint
- https://<account_url>/api/v2/databases/{database}/schemas/{schema}/mcp-servers/{name}
- Authentication
- OAuth 2.0. Snowflake OAuth is the default; an external OAuth identity provider can also be configured. The client uses the security integration�s client ID/secret and each user authenticates with their Snowflake identity. Dynamic client registration is not supported.
Requirements
- A Snowflake account/region that supports Snowflake-managed MCP servers; government regions are currently unsupported per Snowflake documentation.
- A Snowflake administrator or role with the documented privileges to create the MCP server object and OAuth security integration.
- At least one configured/authorized Snowflake tool or object to expose.
Setup steps
- In Snowsight, create an MCP SERVER object in the selected database and schema with the documented `CREATE MCP SERVER � FROM SPECIFICATION` syntax; configure only the tools required for the integration.
- Create or configure a Snowflake OAuth security integration, including the MCP client�s exact redirect URI and an allowed role list. Snowflake-managed MCP does not support dynamic client registration.
- Copy the account URL, database, schema, server object name, and OAuth client ID/secret into the remote MCP client�s secure configuration. The endpoint follows https://<account_url>/api/v2/databases/<database>/schemas/<schema>/mcp-servers/<name>.
- Complete OAuth sign-in and consent in the client, then confirm tools/list returns only tools available to the configured object and the user�s Snowflake role.
Tools
No individual tool names are documented in the reviewed sources.
Tool names and visibility depend on account server configuration, underlying Cortex objects/custom tools, and role permissions.
Limitations and notes
- SYSTEM_EXECUTE_SQL can bypass governed Cortex Agent semantics if exposed on the same server; isolate it and use a least-privilege role.
- The endpoint and available tools are account/configuration specific.
Original sources
- official authentication and connector documentation
Documents OAuth/API integration setup and user authentication for remote MCP connectors.
- verified publisher profile
GitHub organization is verified as controlling snowflake.com; used only as publisher identity/logo provenance, not as proof of MCP behavior.
- official documentation
Current publisher or maintainer documentation reviewed 2026-10-28T19:00:00.000Z.
- official crawl4ai tool inventory audit
Crawl4AI 0.9.5 fetched the selected documentation page. No exact MCP tool identifiers were present in the captured page content; where attempted, the hosted tools/list endpoint required authorization.
- official crawl4ai tool inventory audit
Snowflake-managed MCP tools are defined by the account’s server/Cortex Agent configuration; identifiers vary by deployment, so no global set is published.
Documentation checked 2026-10-28T19:00:00.000Z. Connection has not been runtime tested.
