Changelog — dcs-mcp

The signed launch build.

Code-signed binaries: the server executable and the installer now carry a verified publisher signature (Azure Trusted Signing, timestamped). SmartScreen shows a verified publisher instead of "Unknown"; early-reputation prompts may still appear for a while and are expected.
No functional changes from 0.9.1.

Beta-hardening fix from installer testing.

Microsoft Store builds of Claude Desktop are now supported: the installer registers dcs-mcp in both the classic and Store (packaged) config locations, and the uninstaller cleans up both. If dcs-mcp showed "No servers added" after installing 0.9.0, this release fixes it — run the new installer over your existing install.

Initial open-beta release.

154 mission-authoring tools for Claude: groups, routes, loadouts, triggers, zones, SAM/AWACS/tanker/CAP/SEAD/strike templates, FARPs, carriers, convoys, briefings, kneeboards, F10 drawings, warehouses, weather, terrain-aware placement (line-of-sight, terrain profiles, water checks), and full .miz read/write.
Standalone installer — installs per-user, registers itself with Claude Desktop, no manual config editing.
Terrain support: Caucasus included with the installer; Syria and Kola available now via the built-in Terrain Manager, with more theaters coming during the beta.
Beta licensing: free keys via Discord (/claim), validated online, with a 7-day offline grace window.
Update notifications: dcs-mcp checks for new releases on start and points you here.

Terrain analysis is bare-earth: elevation and line-of-sight don't account for buildings or trees.
Missions edited simultaneously by dcs-mcp and the DCS Mission Editor should be saved by one writer at a time.
The Channel, Normandy, and Marianas WWII are not supported during the beta; support beyond that is to be determined.
Unsigned beta binaries trigger a SmartScreen prompt (see the download page).