Use GliderTrace with OpenCode

GliderMCP

┌ ┐

└ ┘

│

┌ ┐

OpenCode Setup

Configure GliderTrace with OpenCode.

OpenCode

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

dotnet tool install --global glider-trace

OpenCode launches local MCP servers through a command array. Make sure glider-trace is available on PATH.

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

Create opencode.json in your project root. This local command setup uses stdio. OpenCode MCP docs: thdxr.dev.opencode.ai/docs/mcp-servers.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "glider-trace": {
      "type": "local",
      "command": ["glider-trace"],
      "enabled": true
    }
  }
}

Use global config only if you want GliderTrace available across projects.

{
  "mcp": {
    "glider-trace": {
      "type": "local",
      "command": ["glider-trace"],
      "enabled": true
    }
  }
}

If you prefer HTTP, start GliderTrace yourself and configure OpenCode with the local endpoint.

glider-trace --transport http --port 5003

{
  "mcp": {
    "glider-trace": {
      "type": "remote",
      "url": "http://localhost:5003/mcp",
      "enabled": true
    }
  }
}

List configured MCP servers, then ask OpenCode to use GliderTrace for a test or command run.

opencode mcp list
opencode
# Ask: "Use glider-trace to run tests and summarize evidence."

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.

└ ┘