MCP Catalogs
Home

godot-devtool

by wangdiandao·42·Score 45

Godot 4 MCP server for AI-assisted project inspection, editing, validation, and runtime automation.

developer-toolsai-llmproductivity
4
Forks
0
Open issues
this month
Last commit
2d ago
Indexed

Overview

godot-devtool is a comprehensive MCP server that enables AI assistants to interact with Godot 4 projects through multiple transport routes. It provides native, headless, editor, and runtime routes for various workflows including project setup, live editing, runtime testing, and multi-instance management. The server uses stdio communication with optional WebSocket bridging for advanced editor and runtime features. It maintains connection state through project paths, context, and session identifiers, allowing multiple MCP clients to share bridge ports efficiently.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:AI-assisted Godot project setup and configuration
you:Live scene and script editing through AI assistants
you:Automated testing and QA validation during runtime
you:What is the default WebSocket port for the bridge?
you:Does this MCP server require the Godot editor to be running?

When to choose this

Choose godot-devtool if you're using Godot 4 and want AI assistants to help with game development tasks like debugging, scene editing, and runtime automation.

When NOT to choose this

Avoid if you're not using Godot 4, as this server is specifically designed for Godot game development and won't work with other engines.

Tools this server exposes

12 tools extracted from the README
  • get_godot_version

    Get the installed Godot engine version

  • get_capabilities

    Get available tools and their schemas with optional filtering

  • plugin_install

    Install the godot-devtool plugin in a Godot project

  • plugin_status

    Check the installation status of the godot-devtool plugin

  • get_project_info

    Retrieve metadata about a Godot project

  • run_project

    Run the Godot project and capture output

  • stop_project

    Stop the currently running Godot project

  • list_projects

    List Godot projects in a directory

  • project_get_settings

    Read Godot project.godot settings by section or section/key list

  • project_set_setting

    Update Godot project.godot settings with dry-run preview

  • run_project_checks

    Run stable project checks for CI, review, and release workflows

  • browser_visualizer_start

    Start a local read-only dashboard for bridge status and visualization

Comparable tools

godot-mcpgame-dev-assistantgame-mcp-server

Installation

Installation

From Local Build

  1. Extract a published release zip to a stable path
  2. Confirm the server entry exists at build/index.js
  3. Add this MCP server to your client configuration:
{
  "mcpServers": {
    "godot-devtool": {
      "command": "node",
      "args": ["E:/godot-devtool/build/index.js"],
      "env": {
        "GODOT_PATH": "D:/Program Files/Godot/Godot_v4.x.exe",
        "GODOT_DEVTOOL_WS_PORT": "8766"
      }
    }
  }
}

From Source

git clone https://github.com/wangdiandao/godot-devtool.git
cd godot-devtool
npm install
npm run build
  1. Install the Godot plugin using plugin_install tool

FAQ

What is the default WebSocket port for the bridge?
The default WebSocket port is 8766, which can be configured via GODOT_DEVTOOL_WS_PORT environment variable.
Does this MCP server require the Godot editor to be running?
No, it supports both native/headless routes that work without the editor and editor/runtime routes that require the editor or game to be running.

Compare godot-devtool with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.