Godot MCP Runtime

Overview Schema Source Related Servers Discussions Admin

create_scene

Idempotent

Create a new Godot .tscn scene with one root node at a given path, set the root to Node2D, Node3D, or Control, and save it automatically.

Instructions

Create a new Godot scene file with a single root node. Writes a fresh .tscn at scenePath. Use when starting a new scene from scratch; for adding nodes to an existing scene, use add_node. rootNodeType defaults to Node2D - pass "Node3D" for 3D scenes or "Control" for UI. Saves automatically. Overwrites silently if the file already exists. Returns: success and the scenePath that was written. Errors while a Godot runtime session is active on this project; stop_project (or detach_project) clears it.

Input Schema

TableJSON Schema

Name	Required	Description
`scenePath`	Yes	Scene file path relative to the project (e.g. "scenes/main.tscn")
`projectPath`	Yes	Path to the Godot project directory
`rootNodeType`	No	Root node type (default: Node2D)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`success`	No
`scenePath`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.1.1May 17, 2026
Removedv3.0.0May 9, 2026

Changed1 schema field changedv2.3.0May 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "scenePath": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Addedv1.0.0Apr 30, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only provide idempotentHint=true, but the description goes much further: 'Overwrites silently if the file already exists,' 'Saves automatically,' and — critically — 'Errors while a Godot runtime session is active... stop_project (or detach_project) clears it.' This is a runtime precondition no annotation would convey, and it's exactly the kind of behavior that causes agent failures if missed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose, then the routing alternative, then parameter hints, then behavior (overwrite, save), then return shape, then the runtime precondition. Every clause is load-bearing; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values ('success and the scenePath') need not be explained in depth — the description summarizes anyway. Combined with the runtime-session precondition, silent-overwrite warning, and default handling, an agent has everything needed to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaning beyond the schema for rootNodeType by giving concrete values ('pass "Node3D" for 3D scenes or "Control" for UI') and reinforcing the default, which the schema states only in one short clause. No enum is declared in the schema, so this guidance is otherwise unavailable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: 'Create a new Godot scene file with a single root node.' Distinguishes from sibling add_node explicitly, and the write target (.tscn at scenePath) is stated. An agent can identify this tool without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('starting a new scene from scratch') and the alternative for the opposite case ('for adding nodes to an existing scene, use add_node'). Covers the main routing decision cleanly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.