comes from the recent introduction of Model Context Protocol (MCP) support in Unreal Engine 5.8. This allows developers to connect their AI assistant or agent of choice to tools that interact directly with the editor, rather than simply generating code. Although it’s experimental in 5.8, it’s usable! Epic has already made clear its intention to expand the role of AI in Unreal Engine, and developer workflows are likely to evolve alongside it.
“Most major IDEs support coding assistants, and generating code is only part of what they’re good for.”
digging through these, especially when chasing a performance spike or a bug that’s hard to reproduce. The skills flag likely problems and help engineers identify where to look first. The advantage is that once we’ve built something
useful, everyone in the engineering team can benefit from it.
Developers spend countless hours writing
commandlets and attending to automation systems that perform complex operations on batches of assets inside the editor. Being able to hand off some of this workload to an AI agent will sound appealing to most Tech Directors. It frees up developer time to work on the meat of the game.
BUILDING REPEATABLE WORKFLOWS We’ve also been looking at how AI can help with work outside of writing code. At Tanglewood Games, we’ve built a set of Claude Code skills that analyse Unreal Engine artefacts: log files, memory reports and trace files. Engineers can lose hours
LOOKING AHEAD Our Claude Code skills are just one example, and I’m sure other Unreal developers are trying their own approaches. The Unreal community has always been brilliant at sharing what it learns, and I’m excited to see what people come up with, especially when Unreal Engine 6 eventually arrives. Tim Sweeney recently predicted that AI will bring “a new golden age of gaming”, making games viable that would once have cost far more to build than they could earn. That’s hard to picture while the industry is still dealing with widespread layoffs and studio closures. But despite everything, I’d like to believe he’s right.
November/December 2026 MCV/DEVELOP | 41
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52