Skip to main content
Glama
Better Godot MCP

Better Godot MCP

by n24q02m

Better Godot MCP

mcp-name: io.github.n24q02m/better-godot-mcp

Zusammengesetzter MCP-Server für die Godot Engine -- 17 Mega-Tools für KI-gestützte Spieleentwicklung

CI codecov npm Docker License: MIT

TypeScript Node.js Godot Engine semantic-release Renovate

Funktionen

  • 17 zusammengesetzte Mega-Tools -- Szene, Node, Skript, Shader, Animation, Tilemap, Physik, Audio, Navigation, UI und mehr

  • Volle Szenenkontrolle -- Erstellen, Parsen und Ändern von .tscn-Dateien direkt, ohne dass Godot läuft

  • GDScript CRUD -- Erstellen, Lesen, Schreiben und Anhängen von Skripten in einem einzigen Aufruf

  • Gestufte Token-Optimierung -- komprimierte Beschreibungen + help-Tool bei Bedarf

Related MCP server: Godot MCP Unified

Einrichtung

Mit KI-Agent -- kopieren Sie dies und senden Sie es an Ihren KI-Agenten:

Bitte richte @n24q02m/better-godot-mcp für mich ein. Folge dieser Anleitung: https://raw.githubusercontent.com/n24q02m/better-godot-mcp/main/docs/setup-with-agent.md

Manuelle Einrichtung -- folgen Sie docs/setup-manual.md

Tools

Tool

Aktionen

Beschreibung

project

info, version, run, stop, settings_get, settings_set, export

Projekt-Metadaten, Ausführen/Stoppen und Einstellungen

scenes

create, list, info, delete, duplicate, set_main

Szenendatei-Verwaltung

nodes

add, remove, rename, list, set_property, get_property

Manipulation von Szenenbaum-Nodes

scripts

create, read, write, attach, list, delete

GDScript-Datei CRUD

editor

launch, status

Godot-Editor starten und Status prüfen

config

status, set, detect_godot, check

Serverkonfiguration und Umgebungserkennung

resources

list, info, delete, import_config

Ressourcendatei-Verwaltung

input_map

list, add_action, remove_action, add_event

Eingabe-Aktions- und Event-Mapping

signals

list, connect, disconnect

Signalverbindungen

animation

create_player, add_animation, add_track, add_keyframe, list

Animations-Player und Tracks

tilemap

create_tileset, add_source, set_tile, paint, list

TileMap- und TileSet-Verwaltung

shader

create, read, write, get_params, list

Shader-Datei CRUD mit Godot 4-Syntax

physics

layers, collision_setup, body_config, set_layer_name

Kollisionsebenen und physikalische Körper

audio

list_buses, add_bus, add_effect, create_stream

Audio-Bus- und Effektverwaltung

navigation

create_region, add_agent, add_obstacle

Navigationsregionen, Agents und Hindernisse

ui

create_control, set_theme, layout, list_controls

UI-Control-Erstellung und Theming

help

-

Vollständige Dokumentation für jedes Tool abrufen

Konfiguration

Die Godot-Binärdatei wird automatisch an gängigen Installationsorten und im PATH erkannt. Für die grundlegende Verwendung sind keine Umgebungsvariablen erforderlich. Optional können GODOT_PROJECT_PATH und GODOT_PATH gesetzt werden, um die Standardwerte zu überschreiben.

Variable

Erforderlich

Standard

Beschreibung

GODOT_PROJECT_PATH

Nein

-

Standard-Projektpfad (Tools akzeptieren auch den Parameter project_path)

GODOT_PATH

Nein

Automatisch erkannt

Pfad zur Godot-Binärdatei

Einschränkungen

  • Erfordert eine Godot 4.x-Projektstruktur

  • Szenendateien (.tscn) werden durch Textmanipulation geparst/geändert, nicht über die interne API von Godot

  • run/stop/export-Aktionen erfordern eine installierte Godot-Binärdatei

  • Der Docker-Modus hat eingeschränkten Dateisystemzugriff (mounten Sie Ihr Projektverzeichnis)

Sicherheit

  • Binärerkennung -- Multi-Pfad-Godot-Erkennung (Umgebung, PATH, gängige Orte)

  • Projektvalidierung -- Überprüft vor Operationen, ob project.godot existiert

  • Plattformübergreifend -- Pfadbehandlung für Windows, macOS, Linux

Aus Quellcode bauen

git clone https://github.com/n24q02m/better-godot-mcp.git
cd better-godot-mcp
bun install
bun run dev

Lizenz

MIT -- Siehe LICENSE.

Available Tools

17 tools
animationC

Animation management. Actions: create_player|add_animation|add_track|add_keyframe|list. Use help tool for full docs.

Inputs: action (required), loop, name, parent, +7 more. Returns: object

audioC

Audio bus and stream management. Actions: list_buses|add_bus|add_effect|create_stream. Use help tool for full docs.

Inputs: action (required), bus, name, parent, +6 more. Returns: object

configA
Idempotent

Server configuration and environment.

Actions (required params -> optional):

  • status: current config

  • set (key, value): update setting

  • detect_godot: find Godot binary path

  • check: verify project and Godot availability

Inputs: action (required), key, value. Returns: object

editorA
Idempotent

Godot editor control.

Actions (required params -> optional):

  • launch (-> project_path): open editor

  • status (-> project_path): check if editor is running

For running the game, use project(action="run") instead.

Inputs: action (required), project_path. Returns: object

helpA
Read-onlyIdempotent

Full documentation. Omit topic for the overview; use a topic when compressed descriptions are insufficient.

Inputs: topic.

input_mapA
Destructive

Input action management.

Actions (required params -> optional):

  • list (-> project_path): all input actions

  • add_action (action_name -> deadzone=0.5, project_path)

  • remove_action (action_name -> project_path)

  • add_event (action_name, event_type, event_value -> project_path)

event_type: key | mouse | joypad. event_value: e.g., KEY_SPACE.

Inputs: action (required), deadzone, event_type, action_name, +2 more. Returns: object

nodesA
Destructive

Scene node operations.

Actions (required params -> optional):

  • add (scene_path, name -> type="Node", parent=".", project_path)

  • remove (scene_path, name -> project_path)

  • rename (scene_path, name, new_name -> project_path)

  • list (scene_path -> project_path)

  • set_property (scene_path, name, property, value -> project_path)

  • get_property (scene_path, name, property -> project_path)

Node paths: relative to scene root using "/" (e.g., "Player/Sprite2D"). Use "." for root.

Inputs: action (required), name, type, value, +5 more. Returns: object

physicsC

Physics config. Actions: layers|collision_setup|body_config|set_layer_name. Use help tool for full docs.

Inputs: action (required), mass, name, dimension, +6 more. Returns: object

projectA

Godot project operations.

Actions (required params -> optional):

  • info (-> project_path): project metadata

  • version: Godot engine version

  • run (-> scene_path, project_path): launch game

  • logs (-> pid): last captured stdout/stderr lines from a run (default: most recently started)

  • stop: stop running game

  • settings_get (key -> project_path): read project setting

  • settings_set (key, value -> project_path): write project setting

  • export (preset, output_path -> project_path): export game build

Inputs: action (required), key, pid, value, +4 more. Returns: object

resourcesB
Destructive

Resource file management.

Actions (required params -> optional):

  • list (-> type, project_path): browse resources (type: image|audio|font|shader|scene|resource)

  • info (resource_path -> project_path): resource metadata

  • delete (resource_path -> project_path)

  • import_config (resource_path -> project_path): view import settings

Inputs: action (required), type, project_path, resource_path. Returns: object

scenesA
Destructive

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.

Inputs: action (required), new_path, root_name, root_type, +2 more. Returns: object

scriptsA
Destructive

GDScript file CRUD.

Actions (required params -> optional):

  • create (script_path -> extends="Node", content, project_path): generate template

  • read (script_path -> project_path)

  • write (script_path, content -> project_path): replace entire file

  • attach (script_path, scene_path, node_name -> project_path): link to scene node

  • list (-> project_path)

  • delete (script_path -> project_path)

script_path: relative to project root (e.g., "scripts/player.gd").

Inputs: action (required), content, extends, node_name, +3 more. Returns: object

shaderC

Godot shader management. Actions: create|read|write|get_params|list. Use help tool for full docs.

Inputs: action (required), content, shader_path, shader_type, +1 more. Returns: object

signalsA
Destructive

Signal connection management.

Actions (required params -> optional):

  • list (scene_path -> project_path): all signal connections

  • connect (scene_path, signal, from, to, method -> flags, project_path)

  • disconnect (scene_path, signal, from, to, method -> project_path)

Inputs: action (required), to, from, flags, +4 more. Returns: object

tilemapC

TileSet and TileMap management. Actions: create_tileset|add_source|set_tile|paint|list. Use help tool for full docs.

Inputs: action (required), tile_size, scene_path, project_path, +2 more. Returns: object

uiC

UI Control nodes and themes. Actions: create_control|set_theme|layout|list_controls. Use help tool for full docs.

Inputs: action (required), name, type, parent, +5 more. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 17 tools

    Disambiguation4/5

    Each tool targets a distinct Godot subsystem, and explicit notes (e.g., editor launch vs project run) reduce confusion. Some overlap remains between project settings and config, and between scenes and generic resource management.

    Naming Consistency4/5

    Tool names follow a consistent single-noun domain pattern with verb-style actions underneath. Minor inconsistencies like plural scenes/nodes/scripts vs singular animation/shader and the underscore in input_map prevent a perfect score.

    Tool Count4/5

    At roughly 16-17 tools, the server sits at the upper edge of the ideal range, but each tool covers a separate Godot domain and earns its place. It is slightly heavy but not bloated.

    Completeness4/5

    The surface covers the core Godot development lifecycle: project, editor, scenes, scripts, resources, input, signals, rendering, physics, audio, navigation, and UI. Minor gaps exist, such as no generic resource creation and abbreviated documentation for several advanced domains.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers