Official Docs / Model Config

Hardware Status

i9-13900HX | RTX 4060 | 64GB

Chapter 1: Model Configuration (Four Parallel Modes)

To enable seamless UI creation for AI, UMG MCP features four parallel model access mechanisms. Developers can configure their preferred settings within the Unreal Editor at Project Settings -> Unreal Motion Graphics MCP.

1. Four Parallel Modes in Detail

01 Local Model (LiteRT-LM)

Offline / Built-in

How it works: Setting bEnableLiteRtLm = true fires up the built-in C++ LiteRT inference engine inside the editor process. It directly loads local model files (e.g., gemma-4-E2B-it.litertlm) placed in the plugin's Resources/Models directory.

🛠️ Winyunq Hardware Optimization Advice:

To fully leverage your i9-13900HX CPU and RTX 4060 GPU:

  • Configure LocalModelContextLength (Context Length) to 65536.
  • Set LocalModelPrefillChunkSize to 4096 to utilize the parallel execution capabilities of the RTX 4060.

02 Google Account Login (AuthLogin)

OAuth 2.0

How it works: Selecting this launches a secure Google OAuth 2.0 flow managed by UUmgMcpAuthenticationSubsystem. The plugin handles access token retrieval automatically to query Gemini API endpoints without asking developers for manual API keys.

03 API Key Configuration (ApiKey)

Custom Preset

How it works: Configure API credentials for multiple remote model providers. The system ships with presets for Google (Gemini API) and ZhipuAI, alongside a fully customizable Custom preset supporting any OpenAI-compatible endpoints (e.g. DeepSeek, local LM-Studio, or OneAPI gateways).

04 Local Command Line (Local CLI)

Pipe Direct

How it works: Made for automation engineers. Set your primary provider to CLI and fill in the executable command in LocalCliCommand. The plugin launches the console process in the background and pipes conversation payloads via standard I/O (StdIn/StdOut) for low-level execution control.

🔐 API Key Protection & Non-Git Persistence Architecture

In collaborative engineering, a catastrophic mistake is checking sensitive API keys into public Git repositories. To eliminate this vulnerability, UMG MCP leverages Unreal Engine's config architecture to ensure absolute credential isolation:

UI Obfuscation via meta=(Password=true)

Inside `UmgMcpSettings.h`, the API Key properties are annotated with meta=(Password=true). Unreal's Details panel automatically converts the plain text field into masked dots, shielding it from screensharing or video recordings.

Out-of-Git Storage: Saved/Config/WindowsEditor/Editor.ini

Although the settings class is declared as UCLASS(Config = Editor, DefaultConfig), all API Key fields are persisted through runtime-only UPROPERTY(Config) macros. This means:

  • Entering and saving keys inside the editor **never** writes credentials to Config/DefaultEditor.ini (which is tracked by Git).
  • Instead, keys are saved in your local workspace cache at Saved/Config/WindowsEditor/Editor.ini.
  • Under standard Unreal project layouts, the entire Saved/ folder is **strictly ignored** in the project's .gitignore file. Your keys never leave your machine!

📸 Screenshot Slot (Click to expand)

[IMAGE_PLACEHOLDER: Unreal Settings - DeveloperSettings Tab for Unreal Motion Graphics MCP]

Launch Unreal, head to Project Settings, screenshot the "Unreal Motion Graphics MCP" fields, and replace this placeholder card.