Scout setup recommendations

Scout works from any repository with no project to load. These settings help an agent reach for it — and let it power full-workspace search inside Glider and TGlider.

Install globally so it is on PATH

A global scout binary on PATH is what lets Glider and TGlider delegate their search_text to Scout — Glider gains all-language coverage under its solution root, and TGlider needs Scout for search_text at all. Install it globally (or set SCOUT_BINARY_PATH); an npx-only MCP entry runs Scout for that moment only and leaves no binary on PATH, so it does not enable this.

npm install -g @glidermcp/scout
curl -fsSL https://glidermcp.com/install.sh | sh   # Linux/macOS, no Node
brew install glidermcp/tap/scout                   # macOS/Linux

Agent system prompt instruction

Add this product-specific instruction to your MCP client system prompt or project instructions after connecting Scout.

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.

Scope it to the project

Scout resolves its workspace root from the working directory, or pin it with --root <dir>. Prefer a project-scoped MCP config (Claude Code .mcp.json, Cursor .cursor/mcp.json, VS Code .vscode/mcp.json, Gemini CLI .gemini/settings.json, OpenCode opencode.json, Pi .mcp.json) so it indexes the repository you are working in. Scout works in any repository, so Claude Desktop’s single global config is also fine.