AIToday
Large Language ModelsAI Coding AssistantsSnowflake AI BlogPublished: Aug 14, 2026, 06:01 JST4 min read

Snowflake's Observe Launches MCP Server and CLI for AI Agents

Snowflake's Observe Launches MCP Server and CLI for AI Agents

Key takeaway

  • Snowflake's Observe platform has released a redesigned MCP server and new CLI that allow AI agents to query observability data directly—without going through an AI model intermediary.

  • The change reduces latency and cost while enabling engineers to build custom alert-triage and incident-response agents that can autonomously investigate errors and correlate failures across services, or work interactively alongside humans during incident investigations.

3 Key Points

  1. What happened

    Snowflake announced general availability of a redesigned Observe MCP (model context protocol) server and a new Observe CLI with full parity between the two tools. The MCP server now connects AI agents directly to Observe's APIs instead of routing queries through an LLM intermediary, and both tools expose the same operations for agents and engineers.

  2. Why it matters

    Teams are building custom alert-triage agents and incident-investigation copilots that query Observe automatically when alerts fire or during investigations. By removing the LLM middleman and giving agents direct API access, Observe reduces latency and operational cost while letting engineers and AI agents access the same observability capabilities—APM service maps, OpenTelemetry data, and active alerts—through CLI, MCP, or the UI.

  3. What to watch

    General availability is rolling out now across all clusters, with eu-2 and ca-1 regions to follow shortly. Both the CLI and MCP server include a library of prebuilt skills for common observability workflows (incident investigation, failure tracing, change validation, n+1 detection, and outlier detection) that work immediately after configuration.

In Depth

Read the full story

Snowflake announced general availability of a redesigned Observe MCP server and a new Observe CLI, both available rolling out now across all clusters with eu-2 and ca-1 to follow shortly. The two tools offer full operational parity: every operation the MCP server exposes to agents is also available as a CLI command, enabling engineers to choose the interface that fits their workflow—whether connecting custom AI agents, interacting directly from the terminal, or building copilots for incident investigations.

The redesigned architecture represents a significant departure from the original Observe MCP. In the previous version, agents sent queries to a single endpoint where Observe's built-in LLM interpreted the question and returned an answer. This design meant agents lacked direct visibility into Observe's data structure, couldn't explore datasets autonomously, and incurred latency and cost overhead for every interaction. The new MCP server removes the LLM intermediary entirely. Agents now connect directly to Observe's APIs—the same APIs that power Observe's frontend—and can query Observe's context graph themselves. This allows agents to determine which datasets are most valuable to query, write efficient OPAL (Observe's query language), and run precise observability queries against any telemetry data without the latency or cost penalty of the old architecture.

Both the CLI and MCP server ship with a library of prebuilt skills: structured workflows built on how Observe engineers solve common observability tasks. These skills cover incident investigation, failure tracing, change validation, n+1 issue detection, and outlier detection. Both humans and agents can use these skills immediately after configuration without additional setup. Engineers are already using the tools to build custom alert-triage agents that automatically query Observe when an alert fires and pull production telemetry for debugging context, and copilots that work alongside humans during incident investigations. Some workflows run autonomously in the background to handle routine tasks, while others are designed for interactive use where an engineer guides the investigation directly. The new CLI provides programmatic access from agent environments like Claude Code as well as interactive terminal sessions, helping users compose, automate, and extend their observability workflows. 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.

Context & Analysis

The shift reflects a broader trend in AI observability: as agents become the primary consumers of telemetry data—not humans at a dashboard—observability platforms must expose their data through APIs and automation-friendly protocols, not just user interfaces. Snowflake's decision to remove the LLM intermediary is a pragmatic response to advances in foundation models; modern LLMs no longer need Observe to interpret queries on their behalf, and routing through an intermediary layer added cost and latency that customers and engineering teams had already worked around with custom workarounds.

The prebuilt skills and API-first design lower the barrier to entry for engineers building AI-native incident response: teams can now compose and automate observability workflows without building their own integrations or losing the fine-grained data visibility that direct API access provides. By ensuring feature parity between CLI, MCP, and UI—so every operation available to an agent is also available to a human—Snowflake positions Observe for hybrid human-and-agent workflows rather than replacing human judgment with automation.

FAQ

What is the main technical change in the new Observe MCP server?
The original MCP server routed agent queries to a custom LLM that interpreted questions and returned answers. The new architecture removes the LLM middleman, allowing agents to connect directly to Observe's APIs and query the context graph themselves, reducing latency and operational cost.
What can agents and engineers do with the new CLI and MCP server?
Both tools provide the same programmatic access to Observe's capabilities, including APM service maps, OpenTelemetry data collection, and active alert listing. Engineers can build custom alert-triage agents that automatically query Observe when alerts fire, create incident-investigation copilots, update dashboards after investigations, fetch chart images for reports, and query APM errors directly.
When will the new MCP server and CLI be available?
General availability is rolling out now across all clusters, with eu-2 and ca-1 regions to follow shortly.
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 articleOpenAI report finds no link between AI use and revenue gains

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

Sign up free