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"
    }
  }
}

Use a project-local config: Claude Code .mcp.json, Codex .codex/config.toml (trusted projects), Cursor .cursor/mcp.json, or VS Code .vscode/mcp.json. Include portable config files in version control, or copy local config files into each worktree. Git does not copy ignored files. Use absolute paths only when you intentionally want one fixed checkout, such as a global Claude Desktop configuration.

Open the client at the selected worktree root. Relative server arguments use the server launch directory, not the config file directory. Project scope alone does not guarantee that directory. If the client starts elsewhere, configure its MCP working directory or use a Git-root launcher.

Run git rev-parse --show-toplevel in the client terminal, then ask trace_status for the server workspace. Confirm that the loaded solution or workspace belongs to that worktree before you query or change code. For a wrong root, restart GliderTrace with --workspace set to the intended worktree.

An existing HTTP server keeps its own workspace when the client changes directories. Use separate servers and ports for simultaneous worktrees.

git rev-parse --show-toplevel

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.