
What happened
Snowflake announced general availability of a redesigned Observe MCP server and a new Observe CLI with full feature parity, enabling AI agents and engineers to query observability data directly through APIs, model context protocol, and command-line interfaces instead of through the UI alone.
Why it matters
As AI agents increasingly read and act on operational telemetry, observability platforms must support both human and machine access. The new tools let coding assistants investigate errors, AI SREs correlate failures across services, and engineers build custom alert-triage agents that automatically pull production context—without the latency and cost of a language-model intermediary.
What to watch
The redesigned MCP server removes the LLM intermediary built into the original version, giving agents direct access to Observe's APIs and context graph; general availability is rolling out now across all clusters, with eu-2 and ca-1 clusters to follow shortly. Both tools ship with prebuilt skills for incident investigation, failure tracing, and change validation.
Summaries like this, in your inbox every morning.
The shift toward AI agents as primary consumers of operational data is reshaping how observability platforms must function. Historically, telemetry systems were built first for human operators reading dashboards; now, coding assistants, SREs, and alert-handling agents need programmatic, low-latency access to the same data. Snowflake's redesign addresses this by stripping out the cost and latency overhead of an embedded language model that once mediated all agent queries. Instead of an agent asking a question in natural language, which a custom LLM would interpret and answer, the agent now calls Observe's APIs directly—the same APIs that power the web UI. This architectural change reflects broader industry movement: as foundation models improve, the need for domain-specific LLM layers diminishes, making direct API access faster and cheaper.
The availability of full parity between the CLI and MCP server means engineers and agents operate on identical tooling, reducing fragmentation and the need for custom workarounds. The article notes that several teams had already built unofficial integrations because programmatic access was missing; the new tools are designed to cover those use cases (dashboard updates, chart exports, APM error queries) in a supported, efficient way. The inclusion of prebuilt skills—structured workflows for incident investigation, failure tracing, and outlier detection—lowers the barrier to entry: both humans and machines can operate these workflows immediately without custom setup.
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 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.
Cammarata reinterprets InceptionV1's cat-car neuron as a V-shape detector, not two unrelated concepts

Google Deepmind's Gemini 4 Argon scored 97.5 percent on ARC-AGI-3 at a cost of $4,800, second only to GPT-6 As…

Microsoft's Surface Laptop Ultra, using Nvidia's RTX Spark platform, starts at $2,599 (up to $5,899)

Meta's new commercial terms, effective October 30th, appear to let it crawl and train AI on content from websi…

Vercel data published Thursday shows TypeSafe AI's Jev, a lightweight decision model for choosing among predet…

Reflection AI introduced Beam, an open-weight model for agentic coding and long-horizon tasks, with 501 billio…
