Skip to main content
Glama
NAJEMWEHBE

unreal-ai-connection

compile_mod_pak

Compile Unreal Engine mod plugins to .pak files using RunUAT BuildMod or BuildPlugin, headless without UE Editor. Supports game Dev Kits like Conan Exiles, falling back to BuildMod when BuildPlugin is blocked.

Instructions

Compile a UE mod plugin to a .pak file via RunUAT BuildMod (game Dev Kits like Conan Exiles) or BuildPlugin (vanilla UE5), headless. No UE Editor session required. Especially useful for game Dev Kits in 'installed-build mode' where BuildPlugin is blocked (e.g. Conan Exiles Enhanced UE5) — falling back to BuildMod cleanly. BuildMod path produces a .pak in output_dir; BuildPlugin path produces a redistributable plugin package (no .pak generated by default — ok=true based on exit_code alone).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathYesAbsolute path to .uproject (e.g. C:/.../ConanSandbox.uproject)
mod_nameNoMod name; required for BuildMod (matches Content/Mods/<mod_name>/ folder); also used to disambiguate which .pak in output_dir is the intended artefact when multiple are present
plugin_pathNoAbsolute path to .uplugin; required for BuildPlugin
output_dirYesDirectory for output .pak / package (created if missing; required so success can be verified)
uat_commandNoUAT command (BuildMod for game Dev Kits, BuildPlugin for vanilla UE5)BuildMod
run_uat_pathNoOverride path to RunUAT.bat; auto-discovered if not set
extra_argsNoAdditional CLI args appended to RunUAT
timeout_secNoMax wait time (default 30 min)
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It explains the two pathways, their outputs, and that success is based on exit code. Lacks details on system impact, permissions, or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded with the main purpose. It is slightly lengthy but each sentence adds value, covering both pathways and key details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters and no output schema, the description covers the two modes adequately but lacks details on failure modes, error messages, or how to interpret the BuildPlugin output (no .pak generated).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds useful context beyond schema, such as how mod_name disambiguates .pak files and that output_dir is required for success verification.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool compiles a UE mod plugin to a .pak file via two specific methods (BuildMod or BuildPlugin), headless. It distinguishes itself from siblings like compile_blueprint and compile_mod_pak_direct by detailing the two pathways and their outputs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear guidance on when to use BuildMod (game Dev Kits) vs BuildPlugin (vanilla UE5), including fallback for installed-build mode. However, it does not explicitly state when not to use this tool or mention alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NAJEMWEHBE/unreal-ai-connection'

If you have feedback or need assistance with the MCP directory API, please join our Discord server