AIToday
Large Language ModelsAI Coding AssistantsSnowflake AI BlogPublished: Aug 17, 2026, 13:01 JST

Snowflake launches MCP server and CLI for AI agents to access observability data

Snowflake launches MCP server and CLI for AI agents to access observability data

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 to the MCP. The new MCP server removes a custom LLM intermediary layer, allowing agents to connect directly to Observe's APIs and access the same capabilities available in the UI, including APM service maps, OpenTelemetry data collection setup, and active alert listing. The CLI provides programmatic access to Observe's full platform from the command line and works in agent environments like Claude Code as well as interactive terminal sessions.

  2. Why it matters

    Observability platforms must now serve both humans and AI agents, not just people reading dashboards. Engineers are building custom alert-triage agents that automatically query Observe when alerts fire, and copilots that assist during incident investigations. By removing the LLM intermediary, the new architecture cuts latency and operating costs for every agent query, while giving agents direct visibility into Observe's data structure so they can determine which data sets to query and write efficient observability queries.

  3. What to watch

    Both the MCP server and CLI ship with prebuilt skills—structured workflows for common observability tasks like investigating incidents, tracing failures, validating changes, finding n+1 issues, and detecting outliers. These skills work immediately after configuration without additional setup. General availability is rolling out now across all clusters; eu-2 and ca-1 regions will follow shortly.

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

The shift toward AI agents consuming observability data represents a fundamental change in how teams debug and monitor production systems. Previously, telemetry platforms were designed for human operators reading dashboards and dashboards; now agents must be able to programmatically query and reason about operational data at scale. Snowflake's redesign responds directly to this: by removing the LLM intermediary that was built into the original Observe MCP server, the company reduces both the latency and the operational cost of every agent query, while giving agents direct access to Observe's APIs and data structure.

The introduction of the CLI with full parity to the MCP server addresses a concrete developer need. The previous Observe CLI covered only a narrow slice of the platform; most functionality was inaccessible from the terminal. Engineers had built workarounds to fill this gap, and some teams had even constructed their own custom integrations. The new agent-compatible CLI removes this friction by exposing the entire Observe platform—including the ability to update dashboards after an investigation, fetch chart images for automated reports, and query APM errors directly—through both programmatic and interactive interfaces. The prebuilt skills for common observability workflows (incident investigation, failure tracing, change validation, n+1 detection, and outlier detection) lower the barrier to entry: both humans and machines can begin using these workflows immediately after configuration, without custom development.

FAQ
How do I set up the Observe MCP server?
Log into your tenant, go to "Manage account" → "MCP server details", and follow the instructions for your agent of choice.
What capabilities can agents access through the new MCP server?
Agents have access to APM service maps, OpenTelemetry data collection setup in Observe, active alert listing, and the ability to query Observe's context graph directly and write efficient OPAL observability queries against any telemetry data.
How does the new MCP server differ from the original?
The original MCP server had a custom LLM layer that interpreted queries and returned answers; agents had no direct visibility into Observe's data structure. The new server removes this intermediary, allowing agents to connect directly to Observe's APIs and access the same data that powers the frontend, reducing both latency and cost.
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 articleUnique Opto sees AI boost in H1 2026, but H2 outlook cautious