godot mcp

    1

    Automate Godot 4.x project scaffolding, scene tree editing, and resource management via GodotMCP.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    godot mcp

    Example session with this skill installed

    Initialize a new 2D Godot project in GDScript named "SpaceShooter" and create a Player actor with a Camera2D.

    • Read your context and instructions
    • Compiled the godot mcp

    I have initialized the "SpaceShooter" project and configured the base scene hierarchy. The project is set up for 2D gameplay using GDScript, including a main stage and a registered player actor.

    Project Scaffolding Summary

    ComponentActionResult
    Projectinitialize_projectCreated project.godot and folder structure
    Main Scenecreate_sceneInitialized scenes/Main.tscn with Level and UI nodes
    Player Actorcreate_actorCreated scenes/Player.tscn as CharacterBody2D
    Camerascene.add_nodeAttached Camera2D to Player node
    Registrationinstantiate_packed_sceneAdded Player instance to Main/Level

    Next steps

    • Run godot --editor in the SpaceShooter directory to view the generated scenes.
    • Use create_spawnable to add enemy hazards to the ObstacleContainer.
    • Call scene.add_node to add a Sprite2D to the Player actor for visual representation.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Editing Godot project files by hand is fragile: a small mistake in a .tscn or project.godot file can break scenes or project configuration. This skill lets AI agents interact with Godot through godot-mcp instead of generating raw file edits, enabling safer project scaffolding and scene management while significantly reducing token usage.

    What it does

    • Project scaffolding initializes 2D or 3D projects with playable main stages and standardized folder structures.
    • Scene tree management provides precise control to list, add, remove, or rename nodes and update properties without opening the editor.
    • Signal orchestration manages scene connections, allows adding or removing signals, and validates connectivity.
    • Blueprint generation creates actors, spawnable objects, and HUD systems with automatic registration in the main scene.
    • Resource handling manages textures, audio, and custom resources including the generation of .import files.
    • Validation and linting runs project-wide health checks and validates GDScript or C# script syntax via MCP tools.

    How it works

    1. Initialize project using initialize_project to set up the base stage, level containers, and core scripts for GDScript or C#.
    2. Build scene graphs by calling scene.add_node or create_actor to populate the hierarchy with specific node types and properties.
    3. Connect logic via scene.add_connection to wire up signals between nodes or attach scripts using attach_script.
    4. Audit and refine using lint_project or scene.list_nodes to ensure the project structure matches the intended blueprint.

    Frameworks & tools

    Requires Godot 4.x and the godot-mcp (GodotMCP.Server) NuGet package. Optimized for Node 22 LTS and compatible with both GDScript and C# (.NET) workflows.

    Why this beats prompting it yourself

    Writing raw Godot scene files requires strict adherence to resource ordering and load_steps counts that LLMs often hallucinate. This skill uses a dedicated server to perform valid file mutations, ensuring scenes remain readable by the Godot editor.

    Use cases

    • Scaffolding an endless runner blueprint with automated obstacle spawning.
    • Batch updating node properties across multiple scenes without manual clicks.
    • Integrating external assets with auto-generated import configurations.
    • Rapidly prototyping UI hierarchies with CanvasLayer and HUD managers.

    Known limitations

    Requires the GodotMCP.Server to be running locally with the correct GODOT_PATH configured. Does not support Node versions newer than 22 for the MCP Inspector.

    Requires GodotMCP.Server running locally and Godot 4.x. Paths must be absolute or relative to server root. Not compatible with Node versions above 22 LTS for MCP Inspector.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 26 days ago

    Requires

    Godot MCP

    Permissions

    Read Files
    Write Files
    Network Access
    Listed26 days ago

    What's inside

    Frequently Asked Questions

    This skill eliminates manual editing of `.tscn` and `project.godot` files, preventing the common formatting errors and 'load_step' hallucinations that occur when LLMs attempt to write Godot code directly. It provides a reliable bridge to automate scaffolding, scene hierarchy management, and resource imports via a structured server.

    The skill is built for Godot 4.x and supports both GDScript and C# (.NET) workflows. It requires the `godot-mcp` NuGet package and is optimized for Node 22 LTS environments.

    Yes, the skill includes specialized tools for signal orchestration and script attachment. You can programmatically wire connections between nodes and attach existing logic files to the scene tree without ever opening the Godot Editor.

    You will need the GodotMCP.Server running locally with your `GODOT_PATH` environment variable correctly configured. Once the server is active, the AI agent can communicate with your project files through the MCP interface.

    While it is highly efficient for 2D/3D project scaffolding and scene tree manipulation, the MCP Inspector currently does not support Node versions newer than 22. Additionally, the local server must remain active during the session to perform file mutations.

    New in Game Development