Configure Glider with Codex CLI, Codex IDE extension, and Codex app.
dotnet tool install --global glider.dotnet tool install --global gliderglider is available on PATH.# bash/zsh
export PATH="$PATH:$HOME/.dotnet/tools"
which glider~/.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]
command = "glider"
args = ["--default-timeout", "30m"]
startup_timeout_sec = 30
tool_timeout_sec = 1800config.toml.glidermcp from the Codex app Plugin Directory or from the CLI /plugins browser.codex plugin marketplace add glidermcp/glidermcp.comhttp://localhost:5001/mcp. Use only one glider server entry unless you intentionally want separate stdio and HTTP configs.glider --transport http --default-timeout 30m
# ~/.codex/config.toml
[mcp_servers.glider]
url = "http://localhost:5001/mcp"
tool_timeout_sec = 1800/mcp to confirm the server is available.codex
# Then run: /mcpWhen working in C#/.NET workspaces, prefer glider mcp semantic tools before shell text search for code navigation and refactoring. Use GliderMCP for symbol lookup, references, implementations, overrides, callers, call graphs, type and project dependencies, diagnostics, impact analysis, and preview-first refactors. Use grep, rg, or find only for non-C# assets, files outside the loaded workspace, generated output, or after GliderMCP cannot load or cannot answer the question.