Generic MCP Configuration

Configure Scout with any MCP-compatible client.

Install paths

With Node available, the simplest setup runs Scout through npx -y @glidermcp/scout. Machines without Node install the same native binary with the install script or Homebrew.

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

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

Recommendation: Project/Workspace Scope

When possible, configure Scout per project/workspace so it indexes the repository the agent is working in. Scout resolves the workspace root from the working directory (or --root).

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.

Stdio Transport (common: mcpServers JSON)

Many clients use this shape. Replace the file location with your client's recommended project or workspace config file.

{
  "mcpServers": {
    "scout": {
      "command": "npx",
      "args": ["-y", "@glidermcp/scout"]
    }
  }
}

Stdio with the native binary

After installing with the install script or Homebrew, launch the binary directly - no Node involved.

{
  "mcpServers": {
    "scout": {
      "command": "scout"
    }
  }
}

VS Code / Copilot (mcp.json)

VS Code uses a different server map shape. Use this for GitHub Copilot Chat or compatible VS Code MCP flows.

{
  "servers": {
    "scout": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@glidermcp/scout"]
    }
  }
}