Find the Godot project root by searching for project.godot.

List every Godot project under the MCP sandbox directory.

Use this when the MCP process cwd is not inside a project or you need to pick among several games.

Returns: workspace root and a list of {root, name} for each project.godot found

Return the sandbox directory for this server.

Every project path, write, and Asset Library download must stay under this tree unless you change GODOT_MCP_ROOT and restart the server.

Returns: Absolute workspace path and configuration hints

Create a Godot project under the MCP workspace: writes project.godot and a starter .tscn (what the Project Manager also creates on disk). When run_godot_import is true and GODOT_MCP_ALLOW_GODOT_EXEC=1, runs the Godot editor in headless import mode (--import) so the .godot/ cache folder exists and resources are processed—this is the engine's own initialization step; there is no separate "create project" binary in Godot.

Get detailed information about the Godot project.

List all .tscn scene files in the Godot project.

List all .gd script files in the Godot project.

List all .tres resource files in the Godot project.

Find assets by extension.

Read and parse a scene file.

Read and parse a GDScript file.

Create a new GDScript file.

Create a new scene file.

Create a new resource file.

Edit a Godot file by replacing content.

Write content to a file.

Search for content in Godot files.

Find files that may not be referenced in scenes or scripts.

Get information about a Godot node type.

Generate a unique ID for Godot resources.

Returns: A unique ID string

Get project settings from project.godot (read-only).

editor_plugins_enabled lists res:// paths from [editor_plugins]; the user toggles plugins in the Godot editor — MCP does not write that section.

List autoload singletons.

List addon folders with plugin.cfg and which editor plugins are enabled in project.godot.

Use this (and godot_get_project_settings → editor_plugins_enabled) after the user enables plugins in the editor to verify before continuing. MCP installs addons (e.g. godot_download_asset) but does not modify [editor_plugins], to avoid fighting the open editor and external-reload dialogs.

Validate a scene file.

Validate a GDScript file.

Get information about a file.

Find files matching a pattern.

Create code from a template.

Template types:

• character_body_2d: CharacterBody2D script

• character_body_3d: CharacterBody3D script

• node: Basic node script

• resource: Custom resource script

• state_machine: State machine script

Find the Godot executable on the system.

Resolution order when GODOT_EXECUTABLE is unset: macOS: glob (where readable), Spotlight mdfind, find(1) under Applications, then directory scan, then PATH. Windows: where.exe for godot.exe / Godot.exe, then Downloads glob, then directory scan, then PATH. Linux: Downloads / portable names, directory scan, then PATH.

Returns: Dictionary with executable path and version info

Run the Godot game.

Execute a GDScript in the Godot project context.

Check the Godot version.

Get recent Godot log entries.

List scene, script, and/or resource files in the project (for monitoring or refresh).

This server does not run a background file watcher; use the returned paths with your editor or call godot_refresh_project() after external changes.

Refresh project cache after file changes.

Get all files in the project.

Search the official Godot Asset Library.

Get detailed information about an asset.

Download an asset from the Asset Library.

Zip archives are extracted under the project, then any nested .../addons// (with plugin.cfg) is moved to project_root/addons// so res://addons// matches Godot. Editor plugins must be enabled by the user in Project Settings → Plugins (verify with godot_list_editor_plugins).

Search for Godot-related repositories on GitHub.