UStudio Brings Unreal Blueprint Inspection and Local MCP Tools to VS Code

A new third-party extension is trying to narrow the distance between Unreal Engine projects and lightweight code editors. On October 30, 2026, developer Gabriel De la Cruz introduced UStudio, an extension designed for Visual Studio Code and Cursor users who work with Unreal Engine C++ and Blueprints.

The author describes several connected features. One is live execution feedback that highlights C++ calls while a project runs in the editor. Another is the ability to inspect Blueprint asset files in a C++-like representation without launching Unreal Editor for each file. UStudio also offers diagnostics for Unreal Header Tool and linker problems, including proposed edits that can be reviewed as a multi-file difference before being applied.

Its AI-facing component is a local Model Context Protocol server. According to the announcement, the server can provide assistants with context from Blueprint assets, reflected types, and module build definitions. That is a meaningful design target: generic language models often recognize ordinary C++ while missing Unreal-specific reflection, generated headers, and rules that determine whether a project actually compiles.

The developer states that the extension supports Unreal Engine 5.0 through 5.8 for its main parsing workflow, although some editor-driven operations have narrower version requirements. A fully featured fourteen-day Pro trial is advertised. Those statements describe the offered product, not results from independent verification across every release.

Project teams should be cautious with the word 'understands.' A tool may parse a Blueprint sufficiently to display its structure while still failing to represent a complex graph, plugin-defined node, or unusual serialized asset. Similarly, proposed code fixes may be helpful without being correct for every module configuration.

A useful evaluation would use a disposable C++ project containing one Actor class, a Blueprint derived from it, and a deliberately missing module dependency. Test whether UStudio displays the Blueprint accurately, identifies the actual build problem, and proposes a reviewable change. Run a real Unreal compilation afterward rather than accepting an editor's green indicator as proof.

The local MCP integration deserves its own security review. Confirm what files it can read, what context leaves the machine through an AI model, and whether write-capable tools require approval. A local server is not automatically an offline AI workflow.

UStudio is a community product announcement rather than a feature added by Epic. Its value will depend on compatibility, measurement of overhead, and the reliability of its proposed changes in real C++ and Blueprint projects.