AIToday
Large Language ModelsAI Coding AssistantsSnowflake AI BlogPublished: Aug 16, 2026, 04:00 JST

Snowflake Observe adds CLI and redesigned MCP for AI agents to access telemetry directly

Snowflake Observe adds CLI and redesigned MCP for AI agents to access telemetry directly

3 Key Points

  1. What happened

    Snowflake announced general availability of a redesigned Observe MCP server and a new Observe CLI that provide full parity—every operation in the MCP server is also available as a CLI command. The rollout is happening now across all clusters, with eu-2 and ca-1 regions to follow shortly. The new tools let AI agents and engineers query Observe's telemetry data directly through APIs, the MCP (model context protocol), and command line, rather than only through the user interface.

  2. Why it matters

    Observability platforms now need to serve both humans and AI agents. The redesigned architecture removes an LLM intermediary layer, cutting latency and operational cost. Engineers are already using these tools to build custom alert-triage agents that automatically investigate alerts and pull production telemetry for debugging, and copilots that assist during incident investigations—capabilities that require direct, programmatic access to observability data.

  3. What to watch

    Both the CLI and MCP server ship with prebuilt skills for common observability workflows (investigating incidents, tracing failures, validating changes, finding n+1 issues, detecting outliers). The new MCP gives agents direct access to APM service maps, OpenTelemetry data collection setup, and active alert listings. Setup is available now in the Observe UI under "Manage account" → "MCP server details."

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

Observability platforms have historically been built for human operators—dashboards, queries, and alerts designed for engineers to read and act on. Snowflake's announcement reflects a fundamental shift: AI agents are now the primary consumers of telemetry data. Agents can investigate errors before an engineer opens a ticket, correlate failures across services without human intervention, and automate routine debugging tasks. This changes what observability infrastructure must do.

The redesign of the MCP server is instructive. The old version included a custom LLM intermediary that received queries and returned answers, which was expensive and introduced latency. Snowflake removed that layer entirely, letting agents connect directly to Observe's APIs and context graph. This was shaped by feedback from engineering teams already building custom agents—several had built workarounds because programmatic access was limited. The new architecture gives agents visibility into Observe's data structure and permission to explore datasets, enabling more accurate and efficient queries using OPAL (Observe's query language).

The parallel rollout of a full-parity CLI means the same operations available to agents are also available to humans at the command line. Engineers can now compose, automate, and extend observability workflows outside the UI, and agents can work in the same interface as developers—from Claude Code to interactive terminal sessions. The prebuilt skills library (for incident investigation, failure tracing, change validation) lower the barrier to entry, so both humans and machines can start using the tools immediately after configuration.

FAQ
What is the MCP server and why does it matter for AI agents?
The MCP (model context protocol) server lets AI agents connect directly to Observe's platform and query telemetry data without human intervention. The new redesigned version removes a custom LLM layer that was previously built in, allowing agents to access Observe's APIs directly, reducing latency and operational cost.
How does the new CLI differ from the old one?
The previous CLI covered only a narrow slice of Observe's functionality because most operations were inaccessible from the terminal. The new, agent-compatible CLI provides programmatic access to Observe's full capabilities from the command line, with the same surface available through the MCP server and UI, and works in agent environments like Claude Code as well as interactive terminal sessions.
What can engineers use these tools for right now?
Engineers are using the MCP server and CLI to build custom alert-triage agents that automatically query Observe when an alert fires and pull production telemetry for debugging, and copilots that work alongside humans during incident investigations. The tools ship with prebuilt skills for investigating incidents, tracing failures, validating changes, finding n+1 issues, and detecting outliers.
Snowflake AI BlogRead Original Article

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleSpaceX closes $60 billion Cursor acquisition