Godai
com.snopekgamesPublished by snopekgames.comv0.5.0Updated Oct 24, 2026
Automate the Godot Engine editor: edit scenes and scripts, run projects, manage engine versions
Overview
Lets an assistant automate the Godot Engine editor: editing scenes and scripts, running projects, and managing engine versions.
- What you can do
- Godai is a local MCP server that connects an assistant to the Godot Engine editor. According to its registry description, it can automate editor work such as editing scenes and scripts, running projects, and managing engine versions. It runs as a local process over stdio, started with npx from the npm package @snopek-games/godai. No individual tools are listed in the manifest.
- When to use it
- Worth adding when you work in Godot and want an assistant to make scene or script edits, launch projects, or handle engine version management without leaving the editor workflow. It is a desktop-only tool, so it is not suited to headless or web environments.
- Requirements
- A local desktop machine with Node.js available so the npm package @snopek-games/godai can be run with npx over stdio. The manifest declares no authentication, environment variables, or headers. Godot Engine itself is implied by the described functionality.
Installation
In SourceWeft
- Open Godai in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
Tools
0Version history
1- v0.5.0LatestSep 16, 2026
Score
15% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.