AIToday
Large Language ModelsAI Business & IndustrySnowflake AI BlogPublished: Aug 17, 2026, 04:01 JST3 min read

Snowflake's Observe adds AI agent access via MCP server and CLI

Snowflake's Observe adds AI agent access via MCP server and CLI

Key takeaway

  • Snowflake has released a redesigned Observe MCP server and new CLI that give AI agents direct, cost-efficient access to observability data.

  • The key change is removing an internal LLM intermediary; agents now connect straight to Observe's APIs, cutting latency and operational costs while opening new use cases like automated alert triage and incident investigation.

  • Both tools share the same capabilities and come with prebuilt skills for common observability workflows.

3 Key Points

  1. What happened

    Snowflake announced general availability of a redesigned Observe MCP server and new Observe CLI, both offering full parity—every operation exposed to AI agents via the MCP server is also available as a CLI command. The rollout is happening now across all clusters, with eu-2 and ca-1 to follow shortly.

  2. Why it matters

    The new architecture removes an LLM intermediary, letting agents connect directly to Observe's APIs and underlying data structure. This cuts latency, overhead, and operational cost per call, while enabling use cases like automated alert triage and incident investigation copilots that were previously difficult or expensive to build.

  3. What to watch

    Both tools ship with prebuilt skills—structured workflows for common observability tasks (incident investigation, tracing failures, detecting outliers)—that work immediately after configuration. Engineers can access the MCP server by logging into their tenant, navigating to "Manage account" → "MCP server details", and following setup instructions for their chosen agent platform.

Ask the AI about this article →

Context & Analysis

Observability platforms have traditionally been built for human users navigating UIs and dashboards. Snowflake's announcement reflects a fundamental shift: as AI agents take on operational responsibilities—triaging alerts, investigating incidents, correlating failures—observability tools must be redesigned to serve both humans and machines. The old Observe MCP server architecture included an internal LLM to interpret agent queries, a design that made sense when agents and foundation models were less capable. With advances in foundation models, that middleman became unnecessary overhead: agents now understand context graphs and can write precise queries themselves.

The removal of the LLM intermediary is not merely a technical optimization; it solves a practical cost and latency problem that engineering teams had already worked around. By giving agents direct access to the same APIs powering the Observe UI, the new architecture enables faster queries, lower operational costs per call, and more accurate results—agents can examine the data structure and choose which datasets to query before formulating a response. The addition of prebuilt skills (structured workflows for incident investigation, failure tracing, and outlier detection) lowers the barrier to entry: teams can start building agent-driven observability workflows immediately without custom setup.

FAQ

What is the main technical change in the new MCP server?
The redesigned MCP server removes the internal LLM intermediary that was built into the original architecture. Instead of agents sending queries to a single endpoint where Observe's LLM interpreted and answered them, agents now connect directly to Observe's APIs and context graph, enabling them to explore datasets and write efficient queries without the latency and cost of the old LLM middleman.
What can AI agents do with the new MCP server and CLI?
Agents can query Observe directly to investigate errors, correlate failures across services, build custom alert-triage agents that automatically pull production telemetry when an alert fires, and act as copilots during incident investigations. Both tools provide access to APM service maps, OpenTelemetry data collection setup, and active alert listing, with prebuilt skills for common observability tasks like tracing failures and detecting outliers.
Are the MCP server and CLI the same?
The new Observe CLI and MCP server have full parity: every operation the MCP server exposes to agents is also available as a CLI command. The CLI provides programmatic access to Observe's full capabilities from the command line and works in agent environments like Claude Code as well as interactive terminal sessions.
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 articleAnthropic CEO says AI backlash is 'fundamentally a crisis of trust'

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

Sign up free