UESDdebuger - UnityExplorer + SDB Debug

Sometimes, when asking AI to write mods, you end up in this situation:
You give the AI your requirements and specifications (or just make a wish), and it goes off searching Decompilator for tons of information, then writes a bunch of code and completes the mod. But you still have to test it yourself, and reporting errors to the AI too, and the AI scratches its head: "Logically this should work—why does the user say it doesn't?"

So I created (or rather, mostly relied on DeepSeek) this MCP to solve that missing piece of the puzzle.

The purpose of this MCP is simple: let the AI enter the game itself, find red error messages, set breakpoints, identify bugs, and fix them—all automatically, without human intervention. (Hands-free; just sit back and watch.)

Essentially, it enables the AI to directly call:

- RimWorld itself (to debug, the AI needs to be able to start or stop the game)
- DebugAction (the developer menu tools)
- UnityExplorer (built into mods, allows direct inspection of internal game resources and hot-swapping Harmony hooks)
- Unity.mono.debug (similar to Visual Studio or DnSpy—set breakpoints across the entire game, trace issues at the lowest level. Requires modifying the game to enable development mode; the mod includes tutorials)

Additionally, RimBridgeServer and RIMAPI (requires downloading corresponding mods) provide convenient toolsets. Sometimes, saving a save file and letting characters run far away isn’t worth making the AI figure out all these tools.

The latter two don't require configuration and should work right out of the box.

All tools can be individually enabled or disabled. In total, there are 182+2 toolsets (the +2 refers to two tools that can forward calls to nearly all other rarely used tools—no need to clutter the MCP's list with everywhere).