DCS Lua Runner MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DCS_SETTINGS_PATH | No | Path to a custom dcs_lua_runner_settings.json file. If not set, the server looks for the file in its own directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_luaA | Execute arbitrary Lua code on DCS server. Returns the result of the executed code. Use this for custom operations not covered by other tools. |
| get_mission_infoA | Get current mission information including time, theatre, mission name, and weather conditions |
| get_player_infoA | Get information about the player's aircraft including position, altitude, speed, heading, and fuel |
| get_all_unitsA | Get a list of all units in the mission with their properties (coalition, type, position, etc.) |
| spawn_unitA | Spawn a new unit in the mission at specified coordinates. Can use DCS coordinates (x, z) OR real-world coordinates (latitude/longitude or MGRS). |
| send_messageB | Display a message to all players in the mission |
| get_theatre_infoA | Get information about the current theatre/map including terrain type and boundaries |
| get_aircraft_listA | Get a list of all aircraft in the mission with their status |
| convert_coordinatesA | Convert real-world Latitude/Longitude coordinates to DCS X/Z coordinates using the theatre's coordinate system |
| convert_dcs_to_llB | Convert DCS X/Z coordinates to real-world Latitude/Longitude |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
All tools have clearly distinct purposes: coordinate conversion, Lua execution, various queries (aircraft, units, mission, player, theatre), sending messages, and spawning units. No overlapping functionality that would confuse an agent.
All tool names follow a consistent verb_noun pattern in snake_case, such as 'convert_coordinates', 'get_aircraft_list', 'send_message'. No mixing of conventions.
10 tools are appropriate for the server's purpose of interacting with DCS. They cover essential operations without being excessive or too sparse.
The tool set covers major functionalities: coordinate conversion, querying units/aircraft/mission/player/theatre, sending messages, spawning units, and a generic Lua executor. Missing delete/modify operations for units or mission control, but the execute_lua tool can compensate, so only minor gaps.