uloop-get-menu-items
uloop get-menu-items
Retrieve Unity MenuItems.
Usage
uloop get-menu-items [options]
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
--filter-text |
string | - | Filter text |
--filter-type |
string | contains |
Filter type: contains, exact, startswith |
--max-count |
integer | 200 |
Maximum number of items |
--include-validation |
boolean | false |
Include validation functions |
Global Options
| Option | Description |
|---|---|
--project-path <path> |
Target a specific Unity project (mutually exclusive with --port) |
-p, --port <port> |
Specify Unity TCP port directly (mutually exclusive with --project-path) |
Examples
# List all menu items
uloop get-menu-items
# Filter by text
uloop get-menu-items --filter-text "GameObject"
# Exact match
uloop get-menu-items --filter-text "File/Save" --filter-type exact
Output
Returns JSON array of menu items with paths and metadata.
Notes
Use with uloop execute-menu-item to run discovered menu commands.
More from hatayama/uloopmcp
uloop-unity-search
Search Unity project assets using Unity Search engine. Use when you need to: (1) Find scenes, prefabs, scripts, materials, or other assets, (2) Filter assets by file extension or type, (3) Search with Unity Search query syntax and specific providers. Returns asset paths and metadata.
36uloop-clear-console
Clear all Unity Console log entries. Use when you need to: (1) Clear console before running tests or compilation, (2) Start a fresh debugging session, (3) Remove noisy logs to isolate specific output.
36uloop-run-tests
Execute Unity Test Runner and get detailed results. Use when you need to: (1) Run EditMode or PlayMode unit tests, (2) Verify code changes pass all tests, (3) Diagnose test failures with error messages and stack traces. Single-flight only — never run multiple `uloop run-tests` in parallel.
35uloop-launch
Launch Unity project with matching Editor version via uloop CLI. Use when you need to: (1) Open a Unity project with the correct Editor version, (2) Restart Unity to apply changes, (3) Switch build target when launching.
35uloop-get-logs
Retrieve current Unity Console entries via uloop CLI. Use when you need to: (1) inspect errors, warnings, or logs after compile, tests, PlayMode, or dynamic code execution, (2) search current Console messages or stack traces, (3) confirm whether a recent Unity operation emitted logs. Prefer this over reading Editor.log or Unity log files for normal Console contents; use log files only for startup, crash, freeze, or uloop connection failures.
35uloop-control-play-mode
Control Unity Editor play mode (play/stop/pause). Use when you need to: (1) Start play mode to test game behavior, (2) Stop play mode to return to edit mode, (3) Pause play mode for frame-by-frame inspection.
35