Better Godot MCP

Overview Schema Source Related Servers Discussions Admin

scenes

Destructive

Create, list, inspect, delete, duplicate, or set main Godot scene files (.tscn) using paths relative to the project root.

Instructions

Scene file (.tscn) CRUD.

Actions (required params -> optional):

create (scene_path -> root_type="Node2D", root_name, project_path)
list (-> project_path)
info (scene_path -> project_path)
delete (scene_path -> project_path)
duplicate (scene_path, new_path -> project_path)
set_main (scene_path -> project_path)

scene_path: relative to project root (e.g., "scenes/main.tscn"), NOT res:// prefix. Use nodes tool to edit nodes within a scene.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "scenes"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	Action to perform
`new_path`	No	Destination path (for duplicate)
`root_name`	No	Root node name for create
`root_type`	No	Root node type for create (default: Node2D)
`scene_path`	No	Relative scene file path from project root (e.g., "scenes/main.tscn"), not res:// prefix
`project_path`	No	Path to Godot project directory

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.20.0Jul 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

Changed1 schema field changedv1.15.2May 2, 2026

changedInput schema / properties / scene_path / description

Previous value: -"Relative scene file path"New value: +"Relative scene file path from project root (e.g., \"scenes/main.tscn\"), not res:// prefix"

First observedv1.5.1Mar 12, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Matches annotations (destructiveHint: true) with delete action. Clarifies path format (no res://). Could add more on side effects (e.g., implications of set_main).

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?

Compact format with actions listed, then path note. Front-loaded with purpose, no redundant sentences.

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?

Covers all 6 actions and key constraints for a complex tool. Output schema exists, so return values are handled.

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%, but description adds default root_type and path conventions. Provides useful context beyond schema.

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?

Clearly states 'Scene file (.tscn) CRUD' and lists all actions with params. Differentiates from sibling 'nodes' tool, so agent knows this tool manages scene files, not node editing.

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?

Provides action-specific required and optional params in a structured format. Explicitly says to use nodes tool for editing nodes within scenes, guiding correct tool selection.

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

Deploy Server