Use GliderTrace with Codex

GliderMCP

┌ ┐

└ ┘

│

┌ ┐

Codex Setup

Configure GliderTrace with Codex CLI, Codex IDE extension, and Codex app.

Codex

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

dotnet tool install --global glider-trace

Codex starts stdio MCP servers through the configured command. Make sure glider-trace is available on PATH.

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

Edit macOS/Linux ~/.codex/config.toml or Windows %USERPROFILE%\.codex\config.toml. Codex CLI, the IDE extension, and the Codex app share this config. Codex MCP docs: developers.openai.com/codex/mcp.

# ~/.codex/config.toml
[mcp_servers.glider-trace]
command = "glider-trace"
startup_timeout_sec = 30
tool_timeout_sec = 1200

In the Codex app, open Settings > Integrations & MCP to add or manage the same MCP server configuration. Advanced edits still go through config.toml.

The GliderTrace plugin is published from glidermcp/glidermcp.com and bundles the product skill plus stdio MCP config. After adding the marketplace, install glider-trace from the Codex app Plugin Directory or from the CLI /plugins browser.

codex plugin marketplace add glidermcp/glidermcp.com

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

glider-trace --transport http --port 5003

# ~/.codex/config.toml
[mcp_servers.glider-trace]
url = "http://localhost:5003/mcp"
tool_timeout_sec = 1200

Start a new Codex session, then run /mcp to confirm the server is available.

codex
# Then run: /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.

└ ┘