Install Scout

Choose your client and operating system. Follow the three stages below to connect one local workspace.

Operating system

1. Prepare

Requires Node.js 18 or later, with npm. Run this in your terminal. npx selects the current stable package and caches its files. Registry access can be required.

npx -y @glidermcp/scout@latest --version

Install the Pi adapter once:

pi install npm:pi-mcp-adapter

The configuration below checks for the latest stable package at each server start. Restart the server to use an update.

Future packages will expire 90 days after release. Existing versions retain their original expiry. Keep the installed product updated. Update instructions →

2. Connect

Project directory

Use the absolute path to your project directory. The server stays tied to this workspace.

Paths stay in this page. They are not saved or sent to analytics.

Example configuration. Enter your project path before you use it.

Merge this entry into the file below. Keep existing settings and other servers. Replace an existing entry with this name instead of duplicating it.

.mcp.json

{
  "mcpServers": {
    "scout": {
      "command": "npx",
      "args": [
        "-y",
        "@glidermcp/scout@latest",
        "--root",
        "/path/to/MyApp"
      ],
      "cwd": "/path/to/MyApp",
      "requestTimeoutMs": 1800000
    }
  }
}

Pi needs pi-mcp-adapter. This shared project file is read by the adapter; .pi/mcp.json holds Pi-specific overrides.

3. Verify

Restart Pi from the project root. Open /mcp. The adapter connects lazily when you request a server tool.

Ask your agent

Use Scout to check server_status and confirm my repository root. Run one small literal search with find. Report the root and whether coverage is complete. Do not enable semantic search.

The root matches your repository. A complete empty result is valid; partial coverage requires continuation.