Prepare and connect

dotnet tool exec "glider-trace@*" --no-http-cache --verbosity quiet -- --version

Requirements

• .NET 10 SDK installed locally.
• An MCP client that can launch stdio servers or connect to Streamable HTTP.
• Optional .NET diagnostics tools such as dotnet-counters or dotnet-gcdump for collector-specific workflows.

What you can do

• Execute workspace commands and tests, then inspect exit codes, failures, and artifacts.
• Collect counters, traces, or explicitly acknowledged memory dumps.
• Import existing artifacts and query stored sessions.
• Compare failures before and after a change.

Updates

The recommended connection checks for the latest stable package at each server start. See updates and version options.

Next steps

Let your client launch the server over stdio, or run a separate Streamable HTTP server. See HTTP setup.