{ "SchemaVersion": "1", "Kind": "DirectoryIssues", "Slug": "godot-mcp-tomyud1", "Name": "godot-mcp", "CanonicalUrl": "https://askpod.ai/mcp/godot-mcp-tomyud1/issues", "ServerUrl": "https://askpod.ai/mcp/godot-mcp-tomyud1", "IssueTotal": 30, "Held": 23, "Issues": [ { "Title": "Server never connecting (win11/linux/ godot 4.6.1 asset store version)", "Excerpt": "I did everything according to the instructions and plugin is stuck on mpc connecting, tried to do npm install and point to the absolute directory but got the same results, im using LMStudio with mcp.", "SourceUrl": "https://github.com/tomyud1/godot-mcp/issues/10", "PublishedAt": "2026-03-14T13:48:21.000Z", "State": "closed", "Comments": 8, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Add screenshot support", "Excerpt": "Ability to render what the camera is seeing to a screenshot file for the agent to read. Either in editor, or running the game in development. Could allow agents to run the game and visualize what is happening, to inform decisions / fix bugs.", "SourceUrl": "https://github.com/tomyud1/godot-mcp/issues/11", "PublishedAt": "2026-03-14T22:09:23.000Z", "State": "closed", "Comments": 5, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Codex on Windows: Godot connects successfully, then MCP server shuts down and later tool calls fail with \"Transport closed\"", "Excerpt": "## Summary\n\nOn Windows, `godot-mcp-server` starts successfully in Codex and the Godot plugin connects successfully, but the connection drops shortly after when Codex probes the server via `/mcp`. After that, any Godot MCP tool call from Codex fails with:\n\n`Transport closed`\n\nThis appears to be a runtime compatibility / lifecycle issue rather than an installation or initial setup issue.\n\n## Environment\n\n- OS: Windows\n- MCP client: Codex CLI / Codex app\n- Codex version: `0.117.0`\n- Model: `gpt-5.4", "SourceUrl": "https://github.com/tomyud1/godot-mcp/issues/16", "PublishedAt": "2026-03-27T12:34:18.000Z", "State": "closed", "Comments": 4, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Delete .uid files", "Excerpt": "Hi, can i suggest a small behavior addition to delete_script tool? I have been using this MPC and noticed that the .uid files are not being deleted when the script is deleted, which is leaving orphaned .uid files in the project.\n\nIn my project, i added the code below to `godot_mcp/tools/script_tools.gd::delete_script` tool to adjust this behavior:\n```gdscript\n# =============================================================================\n# delete_file\n# ==========================================", "SourceUrl": "https://github.com/tomyud1/godot-mcp/issues/47", "PublishedAt": "2026-05-02T22:38:57.000Z", "State": "open", "Comments": 3, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Feature: configurable timeout and port via environment variables", "Excerpt": "## Problem\n\n1. The 30-second tool timeout (`DEFAULT_TIMEOUT` in `godot-bridge.ts`) is too short for some operations (e.g. `map_project` on large codebases). No way to override without editing source.\n2. The WebSocket port (6505) is hardcoded. Multiple Godot instances or MCP sessions can't coexist.\n\n## Proposed Fix\n\nTwo environment variables:\n- **`GODOT_MCP_TIMEOUT_MS`** — override tool timeout (default: 30000)\n- **`GODOT_MCP_PORT`** — override WebSocket port (default: 6505)\n\n```typescript\nconst ", "SourceUrl": "https://github.com/tomyud1/godot-mcp/issues/20", "PublishedAt": "2026-03-28T22:32:25.000Z", "State": "closed", "Comments": 3, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Feature: classdb_query tool — expose ClassDB to prevent API hallucination", "Excerpt": "## Problem\n\nAI assistants frequently hallucinate non-existent Godot methods (e.g. using Godot 3 API in Godot 4 code, or inventing methods that don't exist). There's no way for the AI to verify that a class, method, or property exists before writing code that uses it.\n\n## Proposed Tool\n\n### `classdb_query`\n- Input: `class_name` (required), `query` (optional: `\"all\"`, `\"properties\"`, `\"methods\"`, `\"signals\"`)\n- Output: properties with types, methods with argument signatures and return types, signa", "SourceUrl": "https://github.com/tomyud1/godot-mcp/issues/19", "PublishedAt": "2026-03-28T22:32:24.000Z", "State": "closed", "Comments": 3, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Feature: run_scene / stop_scene / is_playing tools", "Excerpt": "## Problem\n\nThere's no way for an AI agent to run a scene, check if it's running, or stop it. This means the edit→run→debug loop requires the user to manually press Play in the editor, breaking the autonomous workflow.\n\n## Proposed Tools\n\n### `run_scene`\n- Defaults to main scene\n- Accepts `scene: \"current\"` for the open scene, or a `res://` path for a specific scene\n- Returns error if a scene is already running\n\n### `stop_scene`\n- Stops the currently running scene\n\n### `is_playing`\n- Returns `{ ", "SourceUrl": "https://github.com/tomyud1/godot-mcp/issues/18", "PublishedAt": "2026-03-28T22:32:08.000Z", "State": "closed", "Comments": 3, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "WebSocket server should bind to IPv4 (127.0.0.1) — fixes connection failures", "Excerpt": "## Problem\n\nThe WebSocket server in `godot-bridge.ts` creates a server without specifying a host:\n\n```typescript\nthis.wss = new WebSocketServer({ port: this.port });\n```\n\nThe `ws` library defaults to binding on `::` (IPv6). Godot's `WebSocketPeer` connects to `ws://127.0.0.1:6505` (IPv4). On systems where IPv6 dual-stack doesn't transparently bridge to IPv4, the connection silently fails — the plugin logs `[MCP] Connecting to ws://127.0.0.1:6505...` but never succeeds.\n\nThis is likely the root c", "SourceUrl": "https://github.com/tomyud1/godot-mcp/issues/17", "PublishedAt": "2026-03-28T22:31:57.000Z", "State": "closed", "Comments": 3, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Primary MCP server lingers as orphan after its only stdio client (single DSH) exits, breaking the next session", "Excerpt": "## Summary\n\nWith a **single** MCP client (e.g. DeepSeek Harness DSH, or a lone Codex/Claude session), when the client exits, the **PRIMARY** \\godot-mcp-server\\ process **does not exit** (by design: \\stdin close does NOT kill the server\\). It keeps listening on :6505/:6506 while Godot stays connected.\n\nOn the next launch, the freshly spawned server detects the lingering PRIMARY via the :6506 probe and enters **PROXY mode** against that orphan. If the orphan's stdio is gone but it still holds the ", "SourceUrl": "https://github.com/tomyud1/godot-mcp/issues/66", "PublishedAt": "2026-08-25T18:05:43.000Z", "State": "closed", "Comments": 1, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "run map_project cannot show visual", "Excerpt": "this is cursor tip:\n\n\"\nThe injected JSON is corrupted (unescaped newlines appear).\nThe HTML gets truncated by in the middle of