Use Glider with Codex

Codex Setup

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

Codex

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

dotnet tool install --global glider

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

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

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]
command = "glider"
args = ["--default-timeout", "30m"]
startup_timeout_sec = 30
tool_timeout_sec = 1800

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 Glider plugin is published from glidermcp/glidermcp.com and bundles the product skill plus stdio MCP config. After adding the marketplace, install glidermcp 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 Glider yourself and configure Codex with http://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

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

codex
# Then run: /mcp

Add --solution <path> to the launch arguments in the configuration above so Glider loads your solution or project (a .sln, .slnx, or .csproj file) at startup, instead of waiting for the agent to call load. With it set, server_status shows the workspace as loaded — or, on a large workspace, still loading in the background under workspaceLoading — from the first message, so the agent can wait for that load to finish instead of stopping with a "No solution loaded. Use load first." message and reaching for text search. Put the flag after -- for claude mcp add, add it to the args array in JSON and Codex TOML configs, or to the single command array for OpenCode. Prefer an absolute path — it is machine-specific, so keep it in local or user scope — or a relative path (resolved against the launch directory) when the config is shared in a project.

glider --solution C:/repos/app/src/App.sln --default-timeout 30m
# Add --workspace C:/repos/app to watch a different root, or --no-watch to disable file watching.

After connecting Glider, add this product-specific instruction to your MCP client system prompt or project instructions so the agent chooses the right tool surface first.

When working in C#/.NET workspaces, prefer glider mcp semantic tools for symbol identity, code relationships, diagnostics, dependencies, impact analysis, and preview-first refactors. Use Scout for repository retrieval and raw text questions. Use the .NET CLI for build and test commands. Preload the solution with --solution, or call load before semantic queries.