Other MCP Clients

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

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
[mcp_servers.glider-trace]
command = "glider-trace"
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"
    }
  }
}