Forge Engine MCP Server
Enables AI agents to fully control the Forge Engine (Godot fork) by manipulating scene trees, modifying node properties, and managing game scripts. It allows agents to perform development tasks such as running projects, capturing screenshots, and executing GDScript through a WebSocket connection.
README
🔥 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-server
2. 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 |
|---|---|
forge_get_scene_tree |
Get the full scene tree |
forge_add_node |
Add a node to the scene |
forge_remove_node |
Remove a node from the scene |
forge_get_properties |
Get all properties of a node |
forge_set_property |
Set a property on a node |
forge_screenshot |
Capture the viewport |
forge_run_project |
Run the game |
forge_stop_project |
Stop the game |
forge_get_script |
Get script source code |
forge_set_script |
Update script source code |
forge_execute_gdscript |
Run GDScript code in the editor |
forge_get_output |
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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.