The Connector supports Windows 10 and Windows 11 on both amd64 and arm64.
$
irm https://connector.kuali.co/install.ps1 | iex
Picks the right build for your CPU, downloads to %LOCALAPPDATA%\Programs\kuali\kuali.exe, and adds that folder to your user PATH. No admin rights required. Open a new PowerShell window when it finishes so the updated PATH takes effect.
Download kuali-windows-amd64.exe (most PCs) or kuali-windows-arm64.exe (Copilot+ and other ARM machines) from the latest release, rename it to kuali.exe, then:
$
$dir = "$env:LOCALAPPDATA\Programs\kuali"
$
New-Item -ItemType Directory -Force -Path $dir | Out-Null
$
Move-Item -Force "$HOME\Downloads\kuali-windows-amd64.exe" "$dir\kuali.exe"
Add that folder to your user PATH if it isn't there already, then open a new PowerShell window.
If you use Windows Subsystem for Linux, install the Linux build inside your distro. An AI client running on Windows can still call a Connector installed in WSL — point the MCP config at the WSL binary path (\\wsl$\Ubuntu\home\you\.local\bin\kuali).
Click More info, then Run anyway. You'll only see this once per machine.
$
kuali version
If the command isn't found, PATH likely didn't pick up the new folder — close and reopen PowerShell, or sign out and back in.
$
Remove-Item "$env:LOCALAPPDATA\Programs\kuali" -Recurse -Force
$
Remove-Item "$HOME\.kuali" -Recurse -Force
Remove the PATH entry via Settings → Environment Variables, and delete any kuali-cli entries in Credential Manager → Windows Credentials.
ON THIS PAGE
Once kuali version works, head to Getting started to connect your instance and AI assistant.
Getting started ->Ready-to-use prompts for curriculum, research, build apps, imports, workflow analysis, and reporting.
Browse prompts →Tips for Claude Desktop, Claude Code, Codex, Gemini, Copilot, and VS Code.
AI assistants →Skip the chat — every capability is also a plain kuali command, ready for scripts and CI.
Command reference →