Install on Windows

The recommended Windows package-manager path is Winget:

winget install --id RicardoCabral.icuvisor --exact

Winget downloads the current MSI from the official GitHub release, verifies the installer hash from the package manifest, and installs icuvisor.exe for the current user. Open a new PowerShell or Command Prompt window after installation and confirm:

icuvisor version

To upgrade later:

winget upgrade --id RicardoCabral.icuvisor --exact

Install with PowerShell

The PowerShell installer is also supported. It downloads the latest release asset, verifies the SHA256 checksum, installs icuvisor.exe for the current user, and avoids the unsigned MSI SmartScreen prompt.

iwr -useb https://icuvisor.app/install.ps1 | iex

Open a new PowerShell or Command Prompt window after installation and confirm:

icuvisor version

Re-run the same command to upgrade in place.

icuvisor also ships as an MSI built by CI on every release. The MSI is currently unsigned — Windows SmartScreen may warn about an unknown publisher on first launch. The installer is functional; once past the warning, install, upgrade, and uninstall behave normally.

Install from the MSI manually

1. Download icuvisor_<version>_windows_<arch>.msi and SHA256SUMS.txt from the latest GitHub release. Pick amd64 on Intel/AMD machines and arm64 on ARM (Surface Pro X, Snapdragon laptops).

2. Optional: verify the checksum in PowerShell from the folder where both files were downloaded:

   $msi = "icuvisor_<version>_windows_<arch>.msi"
   (Get-FileHash ".\$msi" -Algorithm SHA256).Hash.ToLower()
   Select-String -Path .\SHA256SUMS.txt -Pattern ([regex]::Escape($msi))

   Replace <version> and <arch> with the file you downloaded. The two hashes must match.

3. Double-click the MSI. When SmartScreen shows “Windows protected your PC”, click More info → Run anyway. This is expected for unsigned pre-v1 builds.

4. The installer is per-user — no UAC prompt. Files land in %LOCALAPPDATA%\Programs\icuvisor, which expands to C:\Users\<you>\AppData\Local\Programs\icuvisor, and that directory is added to your user PATH. AppData is hidden in File Explorer by default, so a normal C: drive search will not find it — paste the path into the address bar, or enable View → Show → Hidden items.

5. Open a new PowerShell or Command Prompt window (existing ones will not have the updated PATH) and confirm:

   icuvisor version

Before you start: API key and athlete ID

You need two things from intervals.icu:

• API key. Log in to intervals.icu, open Settings → Developer Settings, and copy your API key. Setup will ask for this with masked input.
• Athlete ID. It’s displayed near the API key on the page above, or open any page on intervals.icu while logged in and look at the URL — it contains /athlete/i12345/..., where i12345 is your athlete ID. Most IDs are the letter i followed by digits; accounts created by linking Strava have a bare-numeric ID with no i. Either form works.

First-run setup

In a new shell, run:

icuvisor setup

Setup asks for the intervals.icu API key (masked) and your athlete ID, verifies them against intervals.icu, stores the key in Windows Credential Manager under service icuvisor and account intervals-icu-api-key, autodetects your timezone, and writes only non-secret fields to the icuvisor config file. The config may include a credential_ref naming that Credential Manager location, but not the API key.

Useful setup flags:

There is no --api-key flag. Setup always asks for the key interactively so the key is not exposed through shell history or MCP client JSON.

Do not put the API key in Claude Desktop, Claude Code, or any committed config file.

Configure an MCP client

Use this command path in the MCP client configuration:

%LOCALAPPDATA%\Programs\icuvisor\icuvisor.exe

Keep the API key out of client JSON. Put only non-secret values in the client configuration, such as INTERVALS_ICU_ATHLETE_ID, ICUVISOR_TIMEZONE, ICUVISOR_TRANSPORT, or a --config path. For JSON config fields and default config paths, see the config file reference; for environment variables, see the CLI environment variable reference.

Uninstall

1. Quit any MCP clients using icuvisor.

2. Settings → Apps → Installed apps, find icuvisor, click Uninstall. The MSI cleans up files and the per-user PATH entry.

3. Optional: remove the Credential Manager API key:

   cmdkey /delete:icuvisor:intervals-icu-api-key

4. Remove any MCP client config blocks that launch icuvisor.

Build from source

If you would rather not bypass SmartScreen, build the binary yourself with the Go toolchain. See Build from source on the repository README.