Glider MCP v5.3.0
┌ ┐
└ ┘
│
┌ ┐

Codex CLI Setup

Configure Glider with OpenAI Codex CLI.

Codex CLI

dotnet tool install --global glider
You’ll run Glider as a local HTTP server. Make sure glider is available on PATH.
# bash/zsh
export PATH="$PATH:$HOME/.dotnet/tools"
which glider
Codex currently supports MCP servers over Streamable HTTP. Start Glider in HTTP mode (default endpoint: http://localhost:5001/mcp). Add --verbose for logs if needed.
glider --transport http
Edit: macOS/Linux ~/.codex/config.toml, Windows %USERPROFILE%\.codex\config.toml. Codex does not currently support per-repo MCP config, so this is user-scoped. Codex docs: developers.openai.com/codex/mcp.
# ~/.codex/config.toml
[mcp_servers.glider]
url = "http://localhost:5001/mcp"
tool_timeout_sec = 300
Start a new Codex session, then run /mcp to confirm the server is available.
codex
# Then run: /mcp
If you prefer, put Glider under a profile and start Codex with --profile glider. Note: some Codex builds only show globally-configured servers in /mcp; if Glider doesn’t appear, move it back to [mcp_servers.glider].
# ~/.codex/config.toml
[profiles.glider]

[profiles.glider.mcp_servers.glider]
url = "http://localhost:5001/mcp"
tool_timeout_sec = 300

# Run with:
# codex --profile glider
└ ┘