Here's what shipped to customers during the week of September 7, 2026: 4 product areas across 19 merged PRs in 7 repos, part of the Anyshift Product Updates series. The headline is a new public Graph MCP endpoint that lets your own coding agents query the Anyshift graph directly, alongside inline visualizations in Annie's answers, a more accurate CLI, and a PagerDuty fix.

Graph MCP: query your infrastructure graph from your own agents

The Graph MCP endpoint is now live at api.anyshift.io/mcp/graph, so any agent that speaks MCP, including Cursor and Codex, can query your infrastructure graph directly instead of going through the Anyshift web app. Point your own agent at it and ask "what changed on this service last week"; it resolves the answer against the same versioned graph Annie uses for RCAs.

For Claude Code, the Anyshift Agent Plugin reached v0.3.2 this week: a native, portable plugin package that wraps the same event-graph tool surface as Graph MCP, all ten tools from describe_schema to query_graph, with no token or project ID baked into your config since it authenticates through project-scoped OAuth.

Under the hood, the endpoint got a full week of hardening: relative time bounds and window echo on graph queries, clearer notes when a query is missing a Sentry-linked token or targets an unknown label, and larger result pages for teams with big graphs. We also fixed an OAuth bug where MCP clients that omitted a scope in their token request could fail to get a grant issued; that fix is now verified end to end across dev, staging, and production.

Annie's answers get visual

Annie's chat, RCA, and report answers can now render inline visualizations (charts, not just tables and prose), directly in the Anyshift web app and in Slack. The CLI and MCP don't render the chart inline yet; they return a link back to the webapp view for now.

CLI v0.9.0: more accurate graph posture queries

CLI v0.9.0, paired with Graph API v0.2.96, fixes a class of bugs where posture queries, ID briefs, qualified briefs, hotspot scans, and checks, could fall back to a fuzzy name match and return the wrong resource instead of resolving the exact one you asked for. Posture queries now preserve exact resource identity end to end, including legacy resource shapes.

One thing to check before you upgrade: CLI v0.9.0 changes the shape of the CLI's JSON error output. Validation reasons are now included directly on graph query errors instead of being dropped, which is strictly more information, but it does change the contract. If you parse Annie CLI JSON output in a script or CI job, review the new error shape before pinning to v0.9.0.

Fix: PagerDuty on-call identity stays stable

The PagerDuty integration had a bug where an open-ended on-call window could shift identity between polls, which could make Annie's on-call context flicker mid-incident. That's fixed: on-call window identity now stays stable across polls, so the on-call data Annie reasons over during an RCA doesn't move under you.

FAQ

What's new at Anyshift the week of September 7, 2026?

4 product areas shipped across 19 merged PRs in 7 repos. A public Graph MCP endpoint now lets your own agents query the Anyshift graph directly, Annie's answers can render inline visualizations, CLI v0.9.0 fixes graph posture query accuracy, and the PagerDuty integration got an on-call identity fix.

What is the Anyshift Graph MCP?

Graph MCP is a public endpoint at api.anyshift.io/mcp/graph that lets any MCP-speaking agent, including Cursor and Codex, query your infrastructure graph directly. Claude Code users get the same tool surface through the Anyshift Agent Plugin (v0.3.2). It runs on the same versioned graph Annie uses for RCAs. Reference at docs.anyshift.io/pages/product/integration/remote_mcp.

Where can I see Annie's tool output visualizations?

Inline chart visualizations render in Annie's chat, RCA, and report answers in both the Anyshift web app and Slack. The CLI and MCP don't render the chart inline yet; they return a link back to the Anyshift web app.

What changed in CLI v0.9.0?

CLI v0.9.0 and Graph API v0.2.96 fix graph posture queries, ID briefs, qualified briefs, hotspot scans, and checks, so they preserve exact resource identity instead of falling back to a fuzzy name match. It also changes the shape of the CLI's JSON error output, so scripts parsing Annie CLI JSON should check the new schema before upgrading.

What was fixed in the PagerDuty integration?

An open-ended on-call window could shift identity between polls, which made Annie's on-call context flicker mid-incident. PagerDuty on-call window identity now stays stable across polls, so the data Annie reasons over during an RCA doesn't move under you.

That's the week. Try it in the Anyshift product and tell us what it unlocks for your team. We read every reply at app.anyshift.io.