Check Unity Console logs. Use when: checking logs, debugging errors, investigating failures, or when user asks about console output. Key options: --log-type (Error/Warning/Log/All), --max-count, --search-text. Retrieves errors, warnings, and Debug.Log messages.
Quickly install uloop-get-logs AI skill to your development environment via command line
Source: hatayama/uloopmcp.
| --log-type | string | All | Log type filter: Error, Warning, Log, All | | --max-count | integer | 100 | Maximum number of logs to retrieve | | --search-text | string | - | Text to search within logs | | --include-stack-trace | boolean | false | Include stack trace in output | | --use-regex | boolean | false | Use regex for search |
| --search-in-stack-trace | boolean | false | Search within stack trace |
| --project-path | Target a specific Unity project (mutually exclusive with --port). Path resolution follows the same rules as cd — absolute paths are used as-is, relative paths are resolved from cwd. | | -p, --port | Specify Unity TCP port directly (mutually exclusive with --project-path). |
Stable fields and commands for AI/search citations.
npx skills add https://github.com/hatayama/uloopmcp --skill uloop-get-logsCheck Unity Console logs. Use when: checking logs, debugging errors, investigating failures, or when user asks about console output. Key options: --log-type (Error/Warning/Log/All), --max-count, --search-text. Retrieves errors, warnings, and Debug.Log messages. Source: hatayama/uloopmcp.
Open your terminal or command line tool (Terminal, iTerm, Windows Terminal, etc.) Copy and run this command: npx skills add https://github.com/hatayama/uloopmcp --skill uloop-get-logs Once installed, the skill will be automatically configured in your AI coding environment and ready to use in Claude Code, Cursor, or OpenClaw
https://github.com/hatayama/uloopmcp