Forge Engine MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Forge Engine MCP Server Add a Sprite2D node to the scene and set its texture to icon.svg"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🔥 Forge Engine — MCP Server
Let AI agents (Claude, Antigravity, Cursor, etc.) fully control the Godot game engine.
What is this?
This is a Model Context Protocol (MCP) server that connects to a running Forge Engine (Godot fork) instance over WebSocket. It exposes the Forge Protocol as MCP tools, enabling any MCP-compatible AI agent to:
🌲 Manipulate the scene tree — Add, remove, move, duplicate nodes
🔍 Inspect & modify properties — Get/set any node property, connect signals
📸 Capture viewport screenshots — AI can "see" your game
▶️ Run & debug your game — Start, stop, breakpoints, variable inspection
📝 Edit scripts — Read and write GDScript/C# source code
🎮 Simulate input — Click, keyboard, drag in the editor
📦 Manage assets — Import files, create resources
Quick Start
1. Install
npm install -g @forge-engine/mcp-server2. Configure your AI client
Add to your MCP config (e.g., Claude Desktop, Cursor, etc.):
{
"mcpServers": {
"forge-engine": {
"command": "forge-mcp",
"args": ["--port", "6550"]
}
}
}3. Open Forge Engine (Godot fork) with your project
The MCP server will automatically connect to the running editor.
Available Tools
Tool | Description |
| Get the full scene tree |
| Add a node to the scene |
| Remove a node from the scene |
| Get all properties of a node |
| Set a property on a node |
| Capture the viewport |
| Run the game |
| Stop the game |
| Get script source code |
| Update script source code |
| Run GDScript code in the editor |
| Get console output |
Protocol
This MCP server communicates with Forge Engine via the Forge Protocol — a WebSocket-based automation protocol inspired by Chrome DevTools Protocol. See the Forge Protocol Spec for details.
License
MIT — see LICENSE
Available Tools
21 toolsforge_add_nodeC
Add a new node to the Godot scene tree. Specify the parent path, node type (e.g., CharacterBody3D, Sprite2D, Camera3D), and name.
Inputs: parentPath (required), nodeType (required), name (required), properties.
forge_evaluateC
Evaluate a GDScript expression during a debug session.
Inputs: expression (required).
forge_execute_gdscriptB
Execute arbitrary GDScript code in the editor context. Useful for quick automation tasks.
Inputs: code (required).
forge_get_outputC
Get recent console output from the Godot editor.
Inputs: lines.
forge_get_propertiesB
Get all editable properties of a node in the scene, including position, rotation, scale, and type-specific properties.
Inputs: nodePath (required).
forge_get_resolutionA
Get the current viewport resolution (width and height).
Inputs: no named parameters.
forge_get_scene_treeA
Get the full scene tree of the currently open scene in Godot, including all nodes, their types, and hierarchy.
Inputs: no named parameters.
forge_get_scriptB
Read the source code of a GDScript (.gd) or C# (.cs) file.
Inputs: path (required).
forge_get_signalsC
Get all signals available on a node.
Inputs: nodePath (required).
forge_list_filesB
List files and directories in a project path.
Inputs: path.
forge_move_nodeC
Move a node to a new parent in the scene tree.
Inputs: path (required), newParent (required).
forge_open_sceneC
Open a scene file in the Godot editor.
Inputs: path (required).
forge_remove_nodeB
Remove a node from the Godot scene tree by its path.
Inputs: path (required).
forge_run_projectA
Run the Godot project (play the game). Equivalent to pressing F5 in the editor.
Inputs: no named parameters.
forge_save_sceneB
Save the currently edited scene to disk.
Inputs: no named parameters.
forge_screenshotA
Capture a screenshot of the current Godot viewport. Returns a base64-encoded PNG image. Use this to "see" the game or editor state.
Inputs: no named parameters.
forge_set_breakpointC
Set a breakpoint in a GDScript file at a specific line.
Inputs: path (required), line (required).
forge_set_propertyC
Set a property on a node. For example, set position, color, energy, or any exported property.
Inputs: nodePath (required), property (required), value.
forge_set_scriptA
Write/update the source code of a script file. The file will be saved and reloaded in the editor.
Inputs: path (required), source (required).
forge_statusA
Check the connection status to the Forge Engine editor
Inputs: no named parameters.
forge_stop_projectA
Stop the running Godot project. Equivalent to pressing the stop button.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 21 tools
Each tool has a clearly distinct purpose targeting specific Godot editor operations, such as scene manipulation (add_node, move_node, remove_node), debugging (evaluate, set_breakpoint), file handling (list_files, get_script, set_script), and project control (run_project, stop_project). There is no significant overlap in functionality, making tool selection straightforward.
All tool names follow a consistent verb_noun pattern with the 'forge_' prefix, such as forge_add_node, forge_get_scene_tree, and forge_set_property. This uniformity enhances readability and predictability across the toolset.
With 21 tools, the count is slightly high but reasonable for a comprehensive Godot editor integration covering scene management, debugging, file operations, and project control. It provides extensive coverage without being overwhelming, though it borders on the heavy side.
The toolset offers complete coverage for Godot editor interactions, including CRUD operations for nodes and scripts, debugging capabilities, project lifecycle management (run/stop), and utility functions like screenshot and status checks. There are no obvious gaps that would hinder agent workflows in this domain.
Related MCP Connectors
Make games with AI: one MCP server that connects your agent to Unity, Unreal and Godot editors.
Run your Krtuworks apps from an AI agent: setup, remote config, stats, players, bug reports.
Let your coding agent read your GameSalad projects, and edit them live in Creator on Pro and Edu.
The game engine built for AI. Any agent makes a multiplayer game and publishes it.