Skip to main content
Glama
Better Godot MCP

Better Godot MCP

by n24q02m

Better Godot MCP

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

Составной MCP-сервер для Godot Engine -- 17 мега-инструментов для разработки игр с помощью ИИ

CI codecov npm Docker License: MIT

TypeScript Node.js Godot Engine semantic-release Renovate

Возможности

  • 17 составных мега-инструментов -- сцена, узел, скрипт, шейдер, анимация, тайлмап, физика, аудио, навигация, UI и многое другое

  • Полный контроль над сценами -- создание, парсинг и изменение файлов .tscn напрямую без запуска Godot

  • CRUD для GDScript -- создание, чтение, запись и прикрепление скриптов одним вызовом

  • Многоуровневая оптимизация токенов -- сжатые описания + инструмент help по запросу

Related MCP server: Godot MCP Unified

Настройка

С помощью ИИ-агента -- скопируйте и отправьте это своему ИИ-агенту:

Пожалуйста, настрой для меня @n24q02m/better-godot-mcp. Следуй этому руководству: https://raw.githubusercontent.com/n24q02m/better-godot-mcp/main/docs/setup-with-agent.md

Ручная настройка -- следуйте docs/setup-manual.md

Инструменты

Инструмент

Действия

Описание

project

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

Метаданные проекта, запуск/остановка и настройки

scenes

create, list, info, delete, duplicate, set_main

Управление файлами сцен

nodes

add, remove, rename, list, set_property, get_property

Манипуляция узлами дерева сцены

scripts

create, read, write, attach, list, delete

CRUD для файлов GDScript

editor

launch, status

Запуск редактора Godot и проверка статуса

config

status, set, detect_godot, check

Конфигурация сервера и обнаружение окружения

resources

list, info, delete, import_config

Управление файлами ресурсов

input_map

list, add_action, remove_action, add_event

Отображение действий ввода и событий

signals

list, connect, disconnect

Соединения сигналов

animation

create_player, add_animation, add_track, add_keyframe, list

Плееры анимации и треки

tilemap

create_tileset, add_source, set_tile, paint, list

Управление TileMap и TileSet

shader

create, read, write, get_params, list

CRUD для шейдеров с синтаксисом Godot 4

physics

layers, collision_setup, body_config, set_layer_name

Слои коллизий и физические тела

audio

list_buses, add_bus, add_effect, create_stream

Управление аудиошинами и эффектами

navigation

create_region, add_agent, add_obstacle

Навигационные регионы, агенты и препятствия

ui

create_control, set_theme, layout, list_controls

Создание элементов управления UI и тем

help

-

Получить полную документацию для любого инструмента

Конфигурация

Бинарный файл Godot автоматически обнаруживается в стандартных местах установки и в PATH. Для базового использования переменные окружения не требуются. При необходимости установите GODOT_PROJECT_PATH и GODOT_PATH для переопределения значений по умолчанию.

Переменная

Обязательно

По умолчанию

Описание

GODOT_PROJECT_PATH

Нет

-

Путь к проекту по умолчанию (инструменты также принимают параметр project_path)

GODOT_PATH

Нет

Автоопределение

Путь к бинарному файлу Godot

Ограничения

  • Требуется структура проекта Godot 4.x

  • Файлы сцен (.tscn) парсятся/изменяются через текстовую манипуляцию, а не через внутренний API Godot

  • Действия run/stop/export требуют установленного бинарного файла Godot

  • В режиме Docker ограничен доступ к файловой системе (монтируйте директорию вашего проекта)

Безопасность

  • Обнаружение бинарных файлов -- Обнаружение Godot по нескольким путям (env, PATH, стандартные расположения)

  • Проверка проекта -- Проверяет наличие project.godot перед выполнением операций

  • Кроссплатформенность -- Обработка путей для Windows, macOS, Linux

Сборка из исходного кода

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

Лицензия

MIT -- См. 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