Other MCP Clients

Generic GliderTrace configuration for MCP clients that can launch local servers or connect to Streamable HTTP.

Verify the active worktree

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

Install GliderTrace

Install the .NET global tool first, then configure your client to launch glider-trace.

dotnet tool install --global glider-trace

macOS / Windows / Linux: ensure glider-trace is on PATH

Most clients can run glider-trace directly if your .NET tools directory is on PATH.

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

Agent system prompt instruction

Add this product-specific instruction to your MCP client system prompt or project instructions after connecting GliderTrace.

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.

Stdio transport (common mcpServers JSON)

Use this shape for clients that accept a local command in mcpServers.

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

Codex TOML shape

Use this shape for Codex-compatible TOML configuration.

# .codex/config.toml in each worktree
# Launch the MCP server from that worktree root.
[mcp_servers.glider-trace]
command = "glider-trace"
args = ["--workspace", "."]
startup_timeout_sec = 30
tool_timeout_sec = 1200

HTTP transport

For clients that accept a URL in mcpServers, start GliderTrace in HTTP mode first. This example uses port 5003 so it can run beside another local MCP server.

glider-trace --transport http --port 5003

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