Use GliderTrace with Cursor for .NET runtime evidence

GliderMCP

┌ ┐

└ ┘

│

┌ ┐

Cursor Setup

Configure GliderTrace with Cursor IDE.

Cursor

Prerequisite: .NET 10 SDK must be installed before running dotnet tool install --global glider-trace.

dotnet tool install --global glider-trace

Cursor launches stdio MCP servers via command. Make sure glider-trace is available on PATH.

# bash/zsh
export PATH="$PATH:$HOME/.dotnet/tools"
which glider-trace

Create .cursor/mcp.json in your repo. This keeps runtime evidence scoped to the project where the client starts. Cursor MCP docs: https://cursor.com/docs/context/mcp#using-mcpjson.

{
  "mcpServers": {
    "glider-trace": {
      "command": "glider-trace"
    }
  }
}

Create or modify: macOS/Linux ~/.cursor/mcp.json, Windows %USERPROFILE%\.cursor\mcp.json.

{
  "mcpServers": {
    "glider-trace": {
      "command": "glider-trace"
    }
  }
}

If you prefer Streamable HTTP, start GliderTrace yourself and configure Cursor with http://localhost:5003/mcp.

glider-trace --transport http --port 5003

{
  "mcpServers": {
    "glider-trace": {
      "url": "http://localhost:5003/mcp"
    }
  }
}

After connecting GliderTrace, add this product-specific instruction to your MCP client system prompt or project instructions so the agent chooses the right tool surface first.

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.

└ ┘