AIToday
Large Language ModelsAI Coding AssistantsSnowflake AI BlogPublished: Aug 16, 2026, 01:00 JST5 min read

Observe Launches MCP Server and CLI for AI Agents to Query Telemetry Data

Observe Launches MCP Server and CLI for AI Agents to Query Telemetry Data

Key takeaway

  • Snowflake has made its Observe observability platform directly accessible to AI agents by launching a redesigned MCP server and new CLI tool that give agents the same query capabilities available in the Observe user interface.

  • The new architecture removes a costly LLM intermediary and allows agents to connect directly to Observe's APIs, enabling use cases like automated alert triage and incident investigation without engineer intervention.

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 feature parity, enabling AI agents and engineers to query production telemetry directly without going through a UI. The rollout is happening now across all clusters, with eu-2 and ca-1 regions to follow shortly.

  2. Why it matters

    The new architecture removes an LLM intermediary that was previously built into the MCP server, cutting latency and operational costs. Agents can now connect directly to Observe's APIs and query the same data structures available in the UI—allowing coding assistants to investigate errors autonomously, AI SREs to correlate failures across services, and custom alert-triage agents to pull production context automatically when alerts fire.

  3. What to watch

    Both tools ship with prebuilt skills for common observability workflows (incident investigation, failure tracing, n+1 detection, outlier spotting) that work immediately after configuration. Engineers can access the MCP server by logging into their Observe tenant, navigating to "Manage account" → "MCP server details", and following setup instructions for their agent of choice.

In Depth

Read the full story

Snowflake has announced the general availability of a redesigned Observe MCP server and a new Observe CLI, both enabling AI agents and engineers to connect directly to the observability platform's telemetry data. The rollout is happening now across all clusters, with the eu-2 and ca-1 regions to follow shortly. These tools are designed for a world in which AI agents—including coding assistants, AI SREs, and custom alert-triage agents—are primary consumers of observability data alongside humans.

The previous Observe CLI provided only narrow, disconnected access to the platform, as most functionality was locked behind the UI. The new CLI offers full programmatic access to Observe's capabilities from the command line, with identical functionality exposed through the MCP server and the web interface. This enables workflows that can run autonomously in the background to handle routine tasks, as well as interactive investigations where an engineer guides the process. Both tools ship with a library of prebuilt skills—structured workflows for common observability tasks including incident investigation, failure tracing, change validation, n+1 issue detection, and outlier spotting—that work immediately after configuration.

The most significant architectural change is the removal of an LLM intermediary that was built into the original MCP server. Previously, agents would send queries to a single endpoint where Observe's own LLM would interpret the question and return an answer. This design meant agents lacked direct visibility into Observe's data structure and could not explore datasets themselves, creating latency and cost overhead for both Observe and its customers. The rebuilt server eliminates this layer: agents now connect directly to Observe's APIs, the same ones that power the Observe frontend. This gives agents direct access to Observe's context graph, enabling them to determine which datasets are most valuable to query and write efficient OPAL queries against any telemetry data. Agents can now access APM service maps, OpenTelemetry data collection setup, and active alert listings—all the capabilities available in the UI.

Engineering teams using the tools are building custom alert-triage agents that automatically query Observe when an alert fires and pull production telemetry for debugging context, as well as copilots that work alongside humans during incident investigations. To get started, engineers log into their Observe tenant, navigate to "Manage account" → "MCP server details", and follow the instructions for their agent of choice. Snowflake positions this shift as part of a broader recognition that observability is fundamentally a data problem, requiring that observability data be accessible not just through a UI but through the APIs, MCPs, and CLIs that modern AI agents and developer workflows rely on.

Context & Analysis

The shift reflects a broader maturity in AI agent architectures and the observability market. Rather than having agents interact with telemetry through a conversational LLM layer, Snowflake has recognized that direct API access is both cheaper and more reliable—agents no longer incur the latency and cost of an intermediary interpreting queries, and they gain full programmatic visibility into Observe's data structure. This design change was shaped by customer feedback: engineering teams had already built workarounds to access observability data programmatically, indicating market demand that the old UI-and-LLM model did not satisfy.

The introduction of prebuilt skills—structured workflows for common observability tasks like incident investigation and outlier detection—lowers the barrier for teams adopting agent-assisted incident response. By shipping these workflows alongside the API access, Observe is enabling both autonomous and human-guided workflows: agents can triage alerts and pull debugging context without human intervention, while engineers retain the ability to steer investigations interactively. The full parity between the CLI and MCP server means the same capabilities available to agents in Claude Code or other agent environments are also accessible to engineers in terminal sessions, treating observability as a data problem that multiple interfaces should serve equally.

FAQ

How does the new MCP server differ from the old one?
The original MCP server had a custom LLM harness that agents would query, receiving interpreted answers without direct data access. The new server removes that intermediary, allowing agents to connect directly to Observe's APIs and query the context graph themselves, reducing both latency and cost.
What can agents and engineers do with the new CLI and MCP server?
Agents can use these tools to build custom alert-triage agents that automatically query Observe when an alert fires, create copilots for incident investigations, validate changes, trace failures, find n+1 issues, and detect outliers. Both tools expose the full capabilities available in the Observe UI, including APM service maps, OpenTelemetry data collection setup, and active alert listing.
When is this available and where do I start?
General availability is rolling out now across all clusters, with eu-2 and ca-1 regions to follow shortly. To get started, log into your Observe tenant, go to "Manage account" → "MCP server details", and follow the setup instructions for your agent of choice.
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 articleMastercard CEO: Fraud risk to hit $15.6T by 2030, stablecoins key to future

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

Sign up free