Ilvy has three components. Deploy Ilvy Core into each Dynamics 365 environment, host Ilvy Server once for your organization, and give every developer Ilvy Desktop. Each download below shows its latest version, release notes, and a verifiable checksum.
The foundation Ilvy works through. Deploy it once per environment — Dev, UAT and Production each get their own. Requires a Dynamics 365 administrator.
The connector that links your AI assistants to Ilvy Core and governs who can reach which environment. Runs in your own tenant — set it up from scratch or deploy an update over an existing one.
A single self-contained app a developer installs and signs into with their personal access key, then registers with Claude Code or Claude Desktop.
Ilvy.exe somewhere stable —
e.g. %USERPROFILE%\Ilvy\Ilvy.exe. It's a single file; there's no installer.Ilvy.exe configure --seat <YOUR-SEAT-KEY>
Your seat key carries the control-plane address, so there's nothing else to point it at.
⚠ This build isn't code-signed yet, so on first launch Windows
SmartScreen may say "Windows protected your PC" — click More info → Run anyway.One command registers it as a local (stdio) MCP server:
claude mcp add ilvy -- "%USERPROFILE%\Ilvy\Ilvy.exe"
Then check it's connected:
claude mcp list
Open Settings → Developer → Edit Config (this opens
%APPDATA%\Claude\claude_desktop_config.json) and add an ilvy entry under
mcpServers, then fully quit and reopen Claude Desktop:
{
"mcpServers": {
"ilvy": {
"command": "C:\\Users\\you\\Ilvy\\Ilvy.exe"
}
}
}
Use double backslashes in the JSON path,
and the full path (no %USERPROFILE% — JSON doesn't expand it).
ilvy_capabilities — it reports the
environments you've been assigned and which tools this connection allows. Switch environments with
ilvy_switch_profile.Prefer a script? configure-ilvy.ps1
runs the activation (step 2) and can register Claude Code for you with -RegisterClaudeCode.