
Snowflake has made its Observe observability platform directly accessible to AI agents by launching a redesigned MCP server and new CLI that no longer route queries through an internal language model.
Instead, agents now connect directly to Observe's APIs, reducing cost and latency while giving them access to the same data and capabilities the web interface provides.
This enables teams to automate observability tasks such as alert triage and incident investigation without human intervention.
What happened
Snowflake announced general availability of a redesigned Observe MCP server and a new Observe CLI with full parity between them. The MCP server now connects AI agents directly to Observe's APIs instead of routing queries through an internal LLM intermediary, and the CLI provides the same programmatic access from the command line. General availability is rolling out now across all clusters, with eu-2 and ca-1 to follow shortly.
Why it matters
As AI agents increasingly read and act on operational telemetry data, observability platforms must work for both humans and machines. The redesigned tools eliminate the cost and latency overhead of the previous LLM middleman, letting agents query Observe's data structure directly and build custom workflows—such as alert-triage agents that automatically pull production context when alerts fire, or copilots that assist humans during incident investigations. Engineers can now automate observability tasks that previously required UI-based manual work.
What to watch
Both tools ship with a library of prebuilt skills for common observability workflows (investigating incidents, tracing failures, validating changes, finding n+1 issues, detecting outliers) that work immediately after configuration. Access is available through the Observe UI under "Manage account" → "MCP server details"; the CLI works from agent environments like Claude Code as well as interactive terminal sessions.
Snowflake has announced the general availability of two new tools for connecting AI agents to its Observe observability platform: a redesigned MCP (model context protocol) server and a new CLI (command line interface) that provide agents with programmatic access to production telemetry data. General availability is rolling out now across all clusters, with eu-2 and ca-1 regions to follow shortly.
The key innovation is architectural. The previous Observe MCP server included an internal LLM that received queries from agents, performed the reasoning, and returned answers. This design created two problems: it was expensive to operate (Observe bore the cost of running an LLM for every agent query) and it restricted what agents could do (they had no direct visibility into the data structure and could not explore datasets independently). The new MCP server removes this middleman entirely. Agents now connect directly to Observe's APIs—the same APIs that power the web frontend—giving them direct access to the context graph, APM service maps, OpenTelemetry data, and active alerts. This eliminates both the latency and cost of the old design while enabling agents to reason about the data more effectively, since they can determine which datasets are most valuable and write efficient queries directly.
The new CLI provides the same surface. It gives engineers and agents programmatic access to Observe's full platform from the command line, working from interactive terminal sessions as well as agent environments like Claude Code. The previous CLI covered only a narrow slice of the platform's capabilities; the new one provides access to everything available in the UI and MCP server, allowing both humans and machines to compose, automate, and extend observability workflows.
Both tools ship with prebuilt skills—structured workflows built on how Observe engineers solve common observability tasks. These include investigating incidents, tracing failures, validating changes, finding n+1 issues, and detecting outliers. Agents and engineers can use these skills directly without additional setup after initial configuration. In practice, teams are already using the tools to build custom alert-triage agents that automatically query Observe when an alert fires and pull production context for debugging, as well as copilots that work alongside humans during incident investigations. Some workflows run autonomously in the background to handle routine tasks; others are designed for interactive use, requiring an engineer to guide the investigation.
Access is straightforward: engineers log into their Observe tenant, navigate to "Manage account" → "MCP server details", and follow setup instructions for their agent of choice. Snowflake frames this release as part of a shift in how observability is consumed—from a data problem solved primarily by humans reading dashboards to one where AI agents read and act on telemetry directly, making observability accessible to every tool in a development stack.
Observability platforms traditionally served human operators reading dashboards and alerts. Snowflake's announcement reflects a shift in how operational data is consumed: AI agents now read telemetry directly to diagnose failures, correlate events, and propose fixes without waiting for an engineer to investigate. This creates a new set of requirements—observability must work not just through user interfaces but through programmatic interfaces (APIs, MCP, CLI) that agents can call and automate.
The redesign of the Observe MCP server addresses this directly by removing the architectural middleman. The previous version included a built-in LLM that interpreted agent requests, which added cost and latency for every query. By eliminating that layer and giving agents direct access to Observe's underlying APIs, the new server reduces operational overhead while expanding what agents can do—they can now explore the data structure themselves, determine which queries will be most useful, and write efficient queries without relying on an intermediary to reason on their behalf. This design shift mirrors the broader evolution of foundation models: as LLMs became more capable and widely available, the need for a specialized model embedded in each observability tool diminished.
Snowflake positions this as part of a broader vision of observability as a data problem rather than a UI problem. By making telemetry directly accessible to any tool in an engineer's stack—whether an MCP-compatible agent, a CLI, or the web interface—the company is betting that observability workflows will increasingly be automated and integrated into continuous deployment and incident response systems.
AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.
Free · takes 30 seconds · unsubscribe anytime
Ask AI anything about this article. Q&As are published on this page for other readers too.
Morgan Stanley analysts assessed how lower-cost open-weight AI models—which users can download and run on thei…

Apple has formally launched its 'Ads on Maps' platform, allowing businesses to purchase promoted placements in…

Brookfield Corporation has completed acquisitions that expand its life and annuity insurance operations and an…

Alibaba Group's Qwen family of open-weight AI models accumulated more than 3 billion global downloads in the p…

Parnassus Core Equity Fund sold its Salesforce holding in Q2 2026, citing declining conviction in horizontal a…

T-Mobile US has announced a focus on aligning its AI initiatives with customer outcomes, according to reportin…

The AI news that matters, in one minute each morning.
Sign up free