Use GliderMCP with Codex

✈ GliderMCP v6.12.0

┌ ┐

└ ┘

│

┌ ┐

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 GliderMCP plugin bundles the C# workflow skill and stdio MCP config with a 30 minute async-tool timeout. 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

└ ┘