packages-v0.4.95

DBX MCP and CLI 0.4.95 provide precompiled native binaries for macOS, Linux, and Windows.

Recommended npm installation:

```bash
npm install -g @dbx-app/mcp-server@0.4.95
```

Native archives run without Node.js. Download the archive matching your operating system and CPU, verify it with `SHA256SUMS`, extract `dbx-mcp` (or `dbx-mcp.exe`), and configure your MCP client to run it directly.

The CLI archives use the `dbx-cli-*` prefix. Verify them with `CLI-SHA256SUMS`, extract `dbx` (or `dbx.exe`), and run it directly without Node.js.

This package release is separate from the DBX desktop application release and is intentionally not marked as the repository's latest release.


---

## Fix: MCP/CLI could not read desktop-migrated profiles (macOS/Windows)

Desktop provisions the data-encryption key in the OS keychain during the data security upgrade. Previous package builds compiled without any keyring backend, so every desktop-migrated profile made `dbx-mcp` fail on startup with `DATA_MIGRATION_REQUIRED` — even though the migration had already been completed — and the error pointed users back at a wizard they had already finished. Affects every MCP client (Claude Code, Cursor, CodeBuddy, Cline, …) and the CLI.

**Fixed in 0.4.95**: the native macOS and Windows MCP/CLI builds now read the OS keychain. Linux keeps the managed `.dbx/secret.key` file as the key source.

Upgrade:

```bash
npm install -g @dbx-app/mcp-server@0.4.95
```

Notes:
- On macOS the first start may prompt for keychain access to `dbx-mcp` — choose **Always Allow**.
- If you cannot upgrade yet, expose the key to headless tools via the `DBX_SECRET_KEY_FILE` / `DBX_SECRET_KEY` environment variables.