Open Beta · 01 Aug 2026 Public beta opens 1 August 2026. Join the Discord →
dcs-mcp
Overview

What dcs-mcp is

An MCP server that gives Claude read and write access to DCS World .miz mission files. You describe what you want in plain language; Claude uses dcs-mcp's tools to make it real in the file.

The concept

The DCS Mission Editor is powerful, but everything in it is manual: every waypoint clicked, every SAM site placed launcher by launcher, every trigger wired by hand. dcs-mcp moves that work into a conversation.

MCP (Model Context Protocol) is the open standard that lets an AI assistant like Claude use external tools. dcs-mcp is an MCP server whose tools know DCS missions inside out — 154 of them, covering everything from adding a flight to computing a viewshed. When you ask Claude to "stand up an SA-11 site on the ridge east of Fauske and draw its threat ring," Claude picks the right tools, calls them with the right parameters, and the result is written into your actual mission file.

There's no new file format and no lock-in. dcs-mcp reads and writes the same .miz files the Mission Editor uses. Open the result in the editor, fly it in the sim, host it on your server — it's a normal mission.

What it works on

  • Missions — create, open, save; briefing, weather, start time; validation and full-mission reports.
  • Groups & units — planes, helicopters, ships, vehicles, statics; add, modify, clone, move.
  • Flights & AI — CAP, SEAD, strike, escort, intercept, AWACS, and tanker flights with working AI behavior out of the box.
  • Routes — waypoints, tasks, and options, down to per-waypoint detail.
  • Air defense — complete, correctly laid-out SAM sites (SA-series, Patriot, Hawk, NASAMS, IRIS-T, Roland, Rapier, HQ-7), EWR, FARPs, convoys, carrier groups.
  • Triggers, zones & goals — mission logic and scoring.
  • F10 map drawings — circles, lines, polygons, icons, text, in layers.
  • Warehouses — inventories, suppliers, logistics.
  • Terrain — bare-earth elevation, profiles, slope statistics, line-of-sight, viewsheds, water checks, clear-spot search.

The capabilities reference lists every tool, generated from the server itself so it can't drift out of date.

Who it's for

  • Mission builders who want to author and iterate faster — describe the scenario, review it in the editor, refine.
  • Squadron and server admins who maintain rotations of missions and need repeatable, bulk-editable content.
  • The curious who heard "AI that builds DCS missions" and want to see what that actually means.

What it doesn't do

Honest expectations, up front:

  • It edits mission files, not the running sim. It doesn't inject into live sessions or control DCS itself.
  • Flying the mission, in-sim testing, and final hands-on verification stay with you — dcs-mcp gets you a well-built mission fast, but the last look is human.
  • It doesn't replace the Mission Editor; it works alongside it. Many builders keep the editor open to review as they go.
Back up your work. dcs-mcp writes real files. Saves are atomic and deliberate, but any tool that edits your missions deserves a backup habit — keep copies of missions you care about.

Where it runs

dcs-mcp is a local server: your missions never leave your machine except as part of your conversation with Claude. It works with Claude Desktop and Claude Code, and with any other MCP-capable client. Mission editing works on every DCS theater; terrain analysis uses per-theater bare-earth data packs.

Get started →