Browse documentation

.NET runtime evidence

GliderTrace

Run .NET commands and tests, collect runtime evidence, and compare results through MCP.

Install

dotnet tool install --global glider-trace

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

Future packages will expire 90 days after release. Existing versions retain their original expiry. Follow the update guide before expiry.

Next steps

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