glider-trace 0.1.0-preview.1

GliderTrace - Runtime Evidence MCP Server

GliderTrace is a runtime evidence MCP server for C#/.NET agents. It runs workspace-scoped commands and tests, stores bounded evidence, and summarizes failures, exceptions, counters, and runtime traces.

Install

Prerequisite: .NET 10 SDK.

dotnet tool install --global glider-trace

If install fails, run dotnet --version first. If dotnet is missing or below 10, install .NET 10 from: https://dotnet.microsoft.com/download/dotnet/10.0

Run Modes

Stdio (default)

glider-trace

HTTP

glider-trace --transport http

Default HTTP MCP endpoint: http://localhost:5001/mcp

Useful flags:

glider-trace --workspace /path/to/workspace
glider-trace --artifact-root /path/to/workspace/.glider-trace
glider-trace --default-timeout 10m
glider-trace --port 8080
glider-trace --verbose
glider-trace --help
glider-trace --version

--default-timeout supports ms, s, and m suffixes. Use 0 to disable server-side timeout.

Configure Your MCP Client

Use installation and host-specific setup guides on the website:

• https://glidermcp.com/installation
• https://glidermcp.com/installation/codex
• https://glidermcp.com/installation/copilot

Capabilities

• Status and configuration: trace_status
• Runtime command evidence: trace_run
• Test evidence: trace_run_tests
• Session inspection: trace_get_session, trace_query_events, trace_export
• Evidence summaries: trace_exceptions, trace_counters, trace_hotspots

trace_run can collect runtime.nettrace artifacts with built-in EventPipe collection when requested. Counter collection uses dotnet-counters when it is installed.

Artifacts

GliderTrace stores sessions under the artifact root, which defaults to <workspace>/.glider-trace.

Sessions include metadata, normalized evidence events, stdout/stderr artifacts, and optional runtime artifacts. Use trace_export for compact agent summaries or zip artifact references.

Version Expiration

Each GliderTrace version expires 1 month after release date.

dotnet tool update --global glider-trace

Troubleshooting

• If glider-trace is not found after install, ensure ~/.dotnet/tools is on PATH.
• If trace_run rejects a command, check the command policy and use workspace-scoped dotnet commands by default.
• If trace_run_tests cannot find TRX evidence, make sure the target test project supports the requested logger or Microsoft Testing Platform extension.
• If counter collection is unavailable, install dotnet-counters or run without counter collection.

License

All Rights Reserved