Godot MCP

io.github.shin2344234Published by GitHub account shin2344234v0.1.2Updated Oct 26, 2026

Edit Godot 4 scenes, nodes and scripts; run, test and debug games live in the editor or headless.

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Local MCP server that lets an assistant edit Godot 4 scenes, nodes and scripts, and run, test and debug games in the editor or headless.

What you can do
  • Edit project files, scenes, nodes, scripts, signals and resources
  • Run, test and debug games live through the editor bridge or headless Godot
  • Inspect and query the project, editor state and Godot class documentation
  • Work with animation, world, audio, import and export settings
  • Evaluate GDScript inside a running game when explicitly enabled
  • Switch between full per-operation tools and compact router tools, and enable only chosen toolsets
When to use it
Useful when an assistant should work inside an existing Godot 4 project: making scene or script changes, running and debugging the game, or looking up engine documentation without leaving the chat.
Requirements
Runs locally via npx (Node.js). Needs a Godot 4.x executable, set with GODOT_PATH or found on PATH, and the project folder via GODOT_PROJECT_PATH. Optional settings cover timeouts, cache folder, log level, toolset selection, mode and read-only. No authentication declared.
Before you install
GODOT_MCP_ALLOW_EVAL enables running GDScript inside the game, which can do anything the game can, including file and OS calls; it is off by default. Many tools change project files, scenes and scripts. GODOT_MCP_CONFIRM set to 'never' skips confirmation for irreversible operations. GODOT_MCP_READ_ONLY hides all changing tools if you want inspection only.

Installation

In SourceWeft

  1. Open Godot MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.2LatestOct 17, 2026
  2. v0.1.0Oct 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.