.NET runtime evidence

GliderTrace

Runtime evidence MCP server for .NET workspaces.

GliderTrace runs workspace-scoped commands and tests, stores bounded evidence, and summarizes failures, exceptions, counters, runtime traces, and artifacts.

Use it when static code facts are not enough and an agent needs to know what happened when a test, app, or process ran.

Install

dotnet tool install --global glider-trace

Agent Prompt Recommendation

After connecting the server, add a product-specific instruction to the MCP client system prompt so the agent captures runtime evidence instead of defaulting to unstructured terminal output.

System prompt snippet
When you need runtime evidence for .NET code, prefer glider-trace mcp before ad hoc shell runs. Use GliderTrace for test runs, workspace command runs, failure summaries, exception and stack evidence, stdout/stderr summaries, counters, traces, dumps, GC dumps, and artifact indexing. Use plain CLI commands only for simple file operations or commands where no captured evidence or session history is needed.

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.

Common Workflows

  • Run tests and return the first useful failure, exception, stack, stdout, stderr, and TRX evidence.
  • Run a local .NET command and summarize exception-like output, warnings, and artifacts.
  • Capture counters, traces, dumps, or GC dumps when the workflow explicitly needs runtime artifacts.
  • Export compact CI summaries without sending raw sensitive artifacts to the agent context by default.

Run Modes

  • Stdio: the default mode. An MCP client launches glider-trace as a local process.
  • HTTP: run glider-trace --transport http and connect the client to http://localhost:5003/mcp unless you choose another port.

Update Policy

Each GliderTrace release expires one month after its release date.

Update the global tool before or when the server reports that the local build is close to expiry.

dotnet tool update --global glider-trace

GliderTrace Docs

↑/↓ NavigateEnter OpenSpace Expand