Selected projects.

UE4.27.2-focused MCP server for practical editor and content workflows.

Built for teams that still ship on UE4.27 and need automation that respects real editor constraints instead of assuming UE5-era APIs.

• Problem Many Unreal automation examples assume newer engine features, while real projects often stay on UE4.27.2 for years.
• Why it matters Turns common inspection and content tasks into scriptable MCP-friendly workflows while staying grounded in what stock UE4.27 Python can actually support.

• UE4.27.2
• MCP
• Python Remote Execution
• Editor tooling

Standalone Python tools for inspecting UE4.27 .uasset metadata as readable JSON.

Converts binary Unreal assets into review-friendly metadata, focused on package tables, UMG widget summaries, 2-way and 3-way diffs, and P4Merge workflows.

• Problem UE4 .uasset files are binary, so ordinary code review and Perforce change inspection often hide the asset structure that actually changed.
• Why it matters Makes names, imports, exports, dependencies, soft references, and UMG WidgetTrees visible as text without launching Unreal Editor or linking against the engine.

• UE4.27
• Python 3
• UAsset metadata
• UMG
• Perforce P4Merge

Unity Android helper for synchronous StreamingAssets access.

A focused utility for situations where direct file reads are constrained and teams need a predictable loading path without spreading platform-specific logic across the codebase.

• Problem StreamingAssets access on Android is awkward because assets are packaged in ways that make direct synchronous reads harder than they look.
• Why it matters Packages the workaround into a reusable utility so runtime code stays simpler and project code does not need to reinvent the same file-loading edge cases.

• Unity
• Android
• C#
• Runtime tooling