// Capture Unity EditorWindow and save as PNG image. Use when you need to: (1) Take a screenshot of Game View, Scene View, Console, Inspector, etc., (2) Capture visual state for debugging or verification, (3) Save editor output as an image file.
Control Unity Editor play mode via uloop CLI. Use when you need to: (1) Start play mode for testing, (2) Stop play mode after testing, (3) Pause play mode for debugging.
Returns the Unity version. Use this tool to check Unity environment information.
Returns a simple 'Hello World' message. Use this tool for testing MCP connection.
Clear Unity console logs via uloop CLI. Use when you need to: (1) Clear the console before running tests, (2) Start a fresh debugging session, (3) Clean up log output for better readability.
Compile Unity project via uloop CLI. Use when you need to: (1) Verify C# code compiles successfully after editing scripts, (2) Check for compile errors or warnings, (3) Validate script changes before running tests.
Execute C# code dynamically in Unity Editor via uloop CLI. Use for editor automation: (1) Prefab/material wiring and AddComponent operations, (2) Reference wiring with SerializedObject, (3) Scene/hierarchy edits and batch operations. NOT for file I/O or script authoring.
| name | uloop-capture-unity-window |
| description | Capture Unity EditorWindow and save as PNG image. Use when you need to: (1) Take a screenshot of Game View, Scene View, Console, Inspector, etc., (2) Capture visual state for debugging or verification, (3) Save editor output as an image file. |
Capture any Unity EditorWindow by name and save as PNG image.
uloop capture-unity-window [--window-name <name>] [--resolution-scale <scale>]
| Parameter | Type | Default | Description |
|---|---|---|---|
--window-name | string | Game | Window name to capture (e.g., "Game", "Scene", "Console", "Inspector", "Project", "Hierarchy", or any EditorWindow title) |
--resolution-scale | number | 1.0 | Resolution scale (0.1 to 1.0) |
The window name is the text displayed in the window's title bar (tab). The user (human) will tell you which window to capture. Common window names include:
You can also specify custom EditorWindow titles (e.g., "EditorWindow Capture Test").
# Capture Game View at full resolution
uloop capture-unity-window
# Capture Game View at half resolution
uloop capture-unity-window --window-name Game --resolution-scale 0.5
# Capture Scene View
uloop capture-unity-window --window-name Scene
# Capture Console window
uloop capture-unity-window --window-name Console
# Capture Inspector window
uloop capture-unity-window --window-name Inspector
# Capture Project browser
uloop capture-unity-window --window-name Project
# Capture custom EditorWindow by title
uloop capture-unity-window --window-name "My Custom Window"
Returns JSON with:
CapturedCount: Number of windows capturedCapturedWindows: Array of captured window info, each containing:
ImagePath: Absolute path to the saved PNG imageFileSizeBytes: Size of the saved file in bytesWidth: Captured image width in pixelsHeight: Captured image height in pixelsWhen multiple windows of the same type are open (e.g., multiple Inspector windows), all matching windows are captured with numbered filenames (e.g., Inspector_1_*.png, Inspector_2_*.png).
uloop focus-window first if needed