Snapshot debugging MCP for agents
Snapshot debugging MCP for agents
Agents can target an environment and start a snapshot recording for the next matching session, capturing values and call stacks. The agent analyzes the results and can place better snap points and re-arm until the cause is found.
Area: Developer tools. Status: GA. Developer relevance: high. Airtime: 3 min across 2 videos, demoed.
Status evidence
- Nothing said about status; launch event convention: generally available unless stated otherwise.
Where they talk about it
- What's new: Agentic Developer Loop: 2:11 to 4:23, demo at 4:23 (called "Snapshot debugging MCP server" there)
- What's new in AL and Tools: 32:57 to 33:54 (called "Launch snapshot MCP proxy" there)
Quotes
- 3:28 "The snapshot debugging MCP server is built into the standard Microsoft business central MCP infrastructure." - States that snapshot debugging for agents uses the standard Business Central MCP infrastructure, not a separate service.
- 33:27 "Why are these called proxies? This is because the actual work all happens on the server." - Explains the design decision behind the proxy naming.
- 33:38 "There's no snapshot or um performance profiling being done on the client side. It's all being done on the server side." - Clarifies where capture runs, relevant for environment access and expectations.
- 33:54 "this release has been around making agents more capable making it easier for agents to work with the code" - Summarizes the theme of the whole release for AL and tools.
Caveats mentioned
- No snapshot is run on the client, all work happens on the server
- The developer still has to judge what the evidence means
- If the first snapshot lacks information, the agent uses ALSP to find callers and sets snap points elsewhere, then repeats.
Prerequisites mentioned
- The AL tool
- A target environment and tenant
- Snapshot debugging MCP server configured for the Business Central environment
- MCP-capable client such as GitHub Copilot CLI
Documented features match
- Debug recorded Business Central failures with an AI agent - high confidence (llm). Docs say: General availability, roadmap id 573361. Agent records next matching session snapshot
Docs checked on 2026-10-02: the match is against Microsoft's what's new pages for the wave as they were on that date. Microsoft keeps filling the documentation, so "no documented item" can go stale. The wider product documentation on learn.microsoft.com was searched for this feature on the same date; the feature's data lists an article when one was found.
Tags: mcp, snapshot-debugging, agents, debugging, snapshot, al
Generated by pipeline step 06. Source: YouTube auto-captions of the launch event videos, see the deep links. Not official.