Use Scout with Codex

Codex Setup

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

Codex

With Node available, npx -y @glidermcp/scout runs the latest release with no separate install. On machines without Node, install the native binary instead and use scout as the command.

# Linux/macOS
curl -fsSL https://glidermcp.com/install.sh | sh

# Homebrew (macOS/Linux)
brew install glidermcp/tap/scout

Configure Codex to launch Scout over stdio. Scout resolves the workspace root from the working directory, so prefer project/workspace scope when the client supports it.

# ~/.codex/config.toml
[mcp_servers.scout]
command = "npx"
args = ["-y", "@glidermcp/scout"]
startup_timeout_sec = 30
tool_timeout_sec = 60

If you installed the native binary with the install script or Homebrew, launch scout directly instead of going through npx.

# ~/.codex/config.toml
[mcp_servers.scout]
command = "scout"

Start a new client session and ask which Scout tools are available, then try a find query in the workspace.

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 Scout plugin is published from glidermcp/glidermcp.com and bundles the product skill plus stdio MCP config. After adding the marketplace, install scout from the Codex app Plugin Directory or from the CLI /plugins browser.

codex plugin marketplace add glidermcp/glidermcp.com

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

Use the scout mcp find tool as the primary workspace search instead of shell grep, rg, or find. Strict modes (literal, regex, word) are exhaustive; fuzzy is ranked. If glider (C#) or tglider (TypeScript/JavaScript) is installed, prefer it for its language; use scout for every other language and as the universal fallback.