Why web data belongs next to your warehouse
Snowflake’s AI surfaces (Cortex Code, Cortex Analyst, Cortex Agents, Streamlit) are great at orchestrating the data you already own. But the world your data describes lives outside the warehouse, and most of the questions stakeholders actually ask need both. Nimble closes that gap without leaving the Snowflake ecosystem:- Enrich tables in place. Pull current company metadata, product details, or pricing for the rows in a Snowflake table, and write the results straight back as a staging table.
- Validate semantic models against the real world. Check whether the entities a Cortex Analyst semantic model points at still exist, still resolve, still match.
- Ground Streamlit dashboards in live signal. Combine warehouse aggregates with current web context (competitor pricing, news mentions, regulatory updates) in the same view.
- Build Cortex Agents that need the web. Give an agent the same Nimble tools you’d use yourself, so it can research, verify, and gather external context as part of its workflow.
Pick a surface
Cortex Code
Install Nimble MCP in Snowflake’s native AI coding agent. One
cortex mcp add command, OAuth sign-in, full web data toolkit in every Cortex Code session.Cortex Agents
Deploy
NIMBLE_SEARCH and NIMBLE_EXTRACT as scalar Snowflake UDFs callable inline from any SELECT, then wire them into a pre-built Cortex Agent for Snowflake Intelligence.
Data Enrichment
Enrich warehouse tables at scale with
NIMBLE_AGENT_RUN, a SQL-native UDTF for Snowflake. Lateral-join any table with typed structured output from Nimble Web Search Agents — dbt-native, Task-native, no LLM in the loop.Resources
Nimble MCP Server Docs
Full MCP Server setup for Cursor, Claude, and other clients
Snowflake Cortex Code
Snowflake’s docs for the native AI coding agent
Snowflake Cortex Agents
Overview of the Cortex Agents runtime and orchestration model
Snowflake External Access Integration
How Snowflake gates outbound HTTPS from UDFs and stored procedures