I created Didi, a plugin that implements the MCP standard to interface with any AI Agent that recognizes local HTTP interfaces (which is all of them). This is an engine-side MCP server which means it allows the user of an AI Agent to create or modify any aspect of a Godot project as allowed via GDScript (and only GDScript).
Included is an example .md file that can be used to create a tetris game via AI.
It’s available under MIT licensing here: Didi MCP Server Project
I mostly created it for fun but it turned out pretty slick and does what it needs to do… which is allow AI to programmatically work in a project.
One secret to a good MCP server is the resource files it provides back to the AI agent. I plan to keep iterating on those to improve the accuracy and performance of the AI.
1 Like
Interesting approach; if I understand the code correctly, instead of having dedicated tools, Didi lets AI run gdscript to modify the Godot editor state?
1 Like
Exactly – it establishes an interface for the AI to pass a GDScript which the MCP server executes in the main thread of the Editor session. There is a single tool defined in the MCP server which is “run GDScript”. This approach is only limited by the capability of the AI and its ability to compose GDScripts to achieve the requested task.
Performance is enhanced via the resource files provided to the AI Agent. Right now, that’s a single, light-weight GDScript description in .md format. I’ve been tweaking the resource as I walk through some use cases. The first was tetris. I’m nearly finished with a 3D space flight “sim” in an asteroid field. Both have surfaced some enhancements for the .md file. I hope to have the flight sim example (and resource updates) checked in later today.
Then I’ll move onto a real project… rogue-light bullet-hell arena 
Space-flight example pushed along with the addition of a screen-shot tool to the MCP server.