AIToday
Large Language ModelsAI Business & IndustrySnowflake AI BlogPublished: Aug 15, 2026, 16:00 JST4 min read

Snowflake releases AI-agent tools for observability data

Snowflake releases AI-agent tools for observability data

Key takeaway

  • Snowflake has released a redesigned MCP server and new CLI for its Observe observability platform, both enabling AI agents to access telemetry data directly.

  • The key change is removing the old LLM intermediary, which cuts costs and latency by allowing agents to connect straight to Observe's APIs and context graph instead of routing through an intermediary.

  • Engineers can use these tools to build custom alert-triage agents and copilots that investigate incidents autonomously.

3 Key Points

  1. What happened

    Snowflake announced general availability of a redesigned Observe MCP server and new Observe CLI with full parity between them. The rollout is happening now across all clusters, with eu-2 and ca-1 regions to follow shortly. Engineers can now use both tools to connect AI agents directly to Observe's platform for tasks like alert triage and incident investigation.

  2. Why it matters

    Observability platforms must now serve both humans and AI agents accessing telemetry data. The new architecture removes a custom LLM intermediary from the old MCP server, cutting latency and operational costs while giving agents direct access to Observe's APIs and context graph. This enables faster incident response and allows agents to autonomously handle routine observability tasks without an engineer present.

  3. What to watch

    The CLI and MCP server ship with prebuilt skills—structured workflows for common observability tasks like investigating incidents, tracing failures, validating changes, finding n+1 issues, and detecting outliers. Both tools are designed for interactive human use and autonomous agent workflows, and agents can now query Observe directly from environments like Claude Code.

In Depth

Read the full story

Snowflake announced the general availability of a redesigned Observe MCP server and new Observe CLI, both tools built to make observability data accessible to AI agents as well as human engineers. The company recognized a fundamental shift in how telemetry is consumed: coding assistants can now investigate errors before an engineer opens a ticket, and AI site reliability engineers (SREs) can correlate failures across services without human intervention. This places new demands on observability platforms because observability must work for both humans interacting with data through a UI and agents using programmatic interfaces like APIs, model context protocol (MCP), and command line interface (CLI).

The previous Observe CLI covered only a narrow slice of the platform's functionality, as most capabilities were inaccessible from the terminal. The new CLI provides programmatic access to the entire Observe platform, with the same surface area available through the MCP server and the UI. It works in agent environments like Claude Code as well as interactive terminal sessions. Some workflows run autonomously in the background, handling routine tasks without an engineer present, while others are designed for interactive use requiring direct human guidance during incident investigations.

The most significant technical change is architectural. The original MCP server included a custom LLM harness that received user queries, performed reasoning, and returned answers. With advances in foundation models, Snowflake determined this LLM intermediary was no longer necessary. The new architecture removes it entirely, eliminating the expense of passing queries through Observe's own LLM before agents could access data. Instead, agents now connect directly to Observe's APIs and context graph, giving them direct visibility into the data structure, permission to explore datasets, and the ability to write efficient OPAL queries. This design reduces both latency and operational cost for both Snowflake and its customers.

Both the CLI and MCP server ship with a library of prebuilt skills—structured workflows built based on how Observe engineers solve common observability tasks. Agents and engineers can use these skills immediately to investigate incidents, trace failures, validate changes, find n+1 issues, and detect outliers, with no additional setup required after configuration. Through the MCP server, agents have access to the same capabilities available in the Observe UI: APM service maps, OpenTelemetry data collection setup, and active alert listing. General availability is rolling out now across all clusters, with eu-2 and ca-1 regions to follow shortly.

Context & Analysis

The shift toward AI agents as primary consumers of observability data represents a fundamental change in how operational telemetry is accessed and used. Snowflake's redesign reflects feedback from engineering teams already building custom agents for incident response—teams that had previously worked around the lack of programmatic access by building their own solutions. By removing the LLM intermediary from the MCP server architecture, Snowflake addresses both the cost and latency challenges that made the old approach expensive for both the company and its customers.

The full parity between the CLI and MCP server is significant because it means every operation agents can perform is also available to engineers in the command line, creating a unified interface across interactive terminal use, agent-powered automation, and the existing UI. The prebuilt skills—structured workflows for common tasks like tracing failures and detecting outliers—lower the barrier to adoption by eliminating the need for additional setup after configuration. This allows both humans and machines to begin using the tools immediately, addressing a core requirement for observability platforms that must now support dual workflows: some running autonomously in the background and others requiring direct human guidance.

FAQ

Where can I access the Observe MCP server?
Log into your Observe tenant, go to "Manage account" → "MCP server details", and follow the setup instructions for your agent of choice. General availability is rolling out now across all clusters, with eu-2 and ca-1 regions to follow shortly.
What changed between the old and new MCP server?
The old MCP server had a custom LLM intermediary that interpreted queries and returned answers, forcing agents to send queries to a single endpoint without direct data visibility. The new server removes that intermediary, allowing agents to connect directly to Observe's APIs and context graph, reducing both latency and cost.
What can agents do with the new CLI and MCP server?
Agents can query Observe's entire platform programmatically—accessing APM service maps, OpenTelemetry data, active alerts, and executing observability queries via OPAL. Engineers use these tools to build custom alert-triage agents that automatically investigate alerts and pull production telemetry, and copilots that assist during incident investigations.
Snowflake AI BlogRead Original Article

Get the latest Large Language Models news every morning

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · takes 30 seconds · unsubscribe anytime

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleAmkor approves dividend, stock rises on AI-packaging outlook

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

Sign up free