pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for Godot MCP

Pod holds 12 of 12 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to Godot MCP.

Most discussed

On Windows, Godot MCP server does not shut down after claude exits

On Windows, I've configured the .mpc.json in Claude Code as per instructions:

"godot-mcp": {
      "command": "npx",
      "args": ["-y", "@satelliteoflove/godot-mcp"]
    }

The MCP server starts up successfully, and I confirm it connects to the plugin in Godot.

When I close claude, or reconnect to the MCP, the existing server continues running in the background. A second copy of the server is spawned, and attempts to connect to the Godot plugin, and fails:

[godot-mcp] TCP co

[Read the thread](https://github.com/satelliteoflove/godot-mcp/issues/157) · 2026-03-08 · closed · external user · 4 comments

### Feature: Integration Test Harness for End-to-End, Tool, and Performance Testing

Description:

It would be great to have an integration test harness for godot-mcp to enable testing beyond unit-level coverage and better reflect real-world usage.

Potential scope:
	•	End-to-end / full-flow tests (Godot ↔ MCP ↔ client)
	•	Tool invocation tests (schema validation, inputs/outputs, error handling)
	•	Agentic / natural use-case flows (multi-step tool calling, realistic agent behavior)
	•	Regression tests for previously fixed bugs
	•	Performance tests with metrics and statistics (la

[Read the thread](https://github.com/satelliteoflove/godot-mcp/issues/134) · 2026-01-28 · closed · outside contributor · 3 comments

### Feature: Bidirectional Console Logging & Audit Trail

## Overview
Implement bidirectional console/logging integration between Godot and MCP server, with comprehensive audit trails including correlation IDs, timestamps, and user identifiers.

## Motivation

### 🔍 Primary Goal: Visibility & Auditability
Currently, there's a disconnect between Godot's console output and MCP server operations:
- **Godot console messages** (print statements, errors, warnings) are invisible to MCP clients
- **MCP tool executions** are invisible in Godot's console/logs
- 

[Read the thread](https://github.com/satelliteoflove/godot-mcp/issues/126) · 2026-01-28 · closed · outside contributor · 4 comments

### Feature: Daemon + IPC Architecture with Interactive CLI

## Overview
Add daemon process management and IPC (Inter-Process Communication) architecture to godot-mcp, enabling persistent background connections and multiple client modes.

## Motivation

### 🚀 Primary Goal: Performance Through Persistent Connections
The **key improvement** is keeping the Godot WebSocket connection alive between MCP client requests. Without a daemon, each MCP request requires:
1. Starting a new process
2. Establishing WebSocket connection to Godot
3. Executing the request
4

[Read the thread](https://github.com/satelliteoflove/godot-mcp/issues/125) · 2026-01-28 · closed · outside contributor · 4 comments

### README.md MCP config guide update for VSCode GH Copilot, GH Copilot and/or generic guide

## Problem Statement
The godot-mcp server currently only documents configuration for Claude Desktop and Claude Code. Users of other MCP clients (VSCode with GitHub Copilot, GitHub Copilot CLI, and potentially other MCP clients) need clear documentation and configuration examples to use the server.

## Proposed Approach
Expand the README.md to include configuration instructions for VSCode and GitHub Copilot CLI, following the existing pattern used for Claude Desktop and Claude Code. Alternatively

[Read the thread](https://github.com/satelliteoflove/godot-mcp/issues/124) · 2026-01-28 · closed · outside contributor · 4 comments

### Feature: Godot MCP Plugin Module System

# Godot MCP Plugin Module System Implementation Plan

## Problem Statement
The current Godot MCP plugin is monolithic - all components are loaded in `plugin.gd` and a crash in any component brings down the entire plugin. During development and usage of the MCP system, errors in command handlers, WebSocket issues, or connection problems require a full plugin restart, which is disruptive and time-consuming.

## Proposed Solution
Refactor the plugin into a slim, robust core (`plugin.gd`) that dynam

[Read the thread](https://github.com/satelliteoflove/godot-mcp/issues/123) · 2026-01-28 · closed · outside contributor · 4 comments

### Websocket instability: "awaiting WebSocket handshake"

I'm running into stability issues that seem to be coming from the websocket connection between the MCP server and the Godot addon. While the tool calls do occasionally function, many simply return with:

`Error:
Error: Not connected to Godot` 

from my MCP client (Cline).

I'm also noticing a lot of log events on the Godot side where the plugin initializes, sees a tcp connection and first websocket connection, but then seems to keep failing or resetting after that.

Godot Output Console: 

> [go

[Read the thread](https://github.com/satelliteoflove/godot-mcp/issues/74) · 2026-01-06 · closed · external user · 10 comments

### Error when using claude opus 4.5 in google antigravity

When i ask "What is the current scene in godot?" with model  claude opus 4.5 im receiving error: Agent terminated due to error
You can prompt the model to try again or start a new conversation if the error persists.
See our [troubleshooting guide](https://antigravity.google/support) for more help.

But when i change my model to gemini 3 pro (high) its works correctly

[Read the thread](https://github.com/satelliteoflove/godot-mcp/issues/24) · 2025-12-21 · closed · external user · 2 comments

## Most recent

### Possible fix(deps): 9 vulnerable dependencies in package-lock.json

This might be a false positive, but `server/package-lock.json` around line 1987 looked worth a second pair of eyes.

The project uses fast-uri 3.1.0, which is vulnerable to CVE-2026-13676. The library fails to correctly canonicalize Unicode (IDN) hostnames, allowing an attacker to craft URLs that bypass host‑based security checks (e.g., deny‑lists, loopback filters) when the URL is later parsed by Node's native URL or fetch APIs. This can lead to unauthorized redirects, proxy abuse, or access to

[Read the thread](https://github.com/satelliteoflove/godot-mcp/issues/377) · 2026-08-26 · open · external user · 0 comments

### save_scene: explicit scene_path writes active tab's content to the given path (content/target mismatch)

Version: godot-mcp-v4.1.0 (source build)

The `godot_scene` tool's `save` action resolves its target from the
caller's `scene_path` parameter, but always packs the editor's currently
active scene (`EditorInterface.get_edited_scene_root()` in
scene_commands.gd's save_scene). There is no check that the resolved path
belongs to the active scene.

Result: calling save with an explicit `scene_path` that is not the active
tab's own file silently overwrites the target file with the active
scene's conte

[Read the thread](https://github.com/satelliteoflove/godot-mcp/issues/346) · 2026-08-23 · closed · external user · 1 comment

### Tools not exposed when Godot connection fails at startup; no diagnostic surfaced to user

**Environment:** WSL2 (Claude Code running in WSL) + Godot running on Windows

**What happened:**

1. The MCP server started (via `npx`) at Claude Code session launch with Godot in **Localhost** bind mode (`127.0.0.1:6550`)
2. From WSL, `127.0.0.1` does not reach the Windows host — connection to Godot failed silently
3. The MCP server started successfully (it responded to MCP protocol calls, e.g. resource listing), but **registered zero tools** with the client
4. Claude Code showed no `godot-mcp

[Read the thread](https://github.com/satelliteoflove/godot-mcp/issues/319) · 2026-06-13 · closed · external user · 1 comment

### MCP server instances replace each other when multiple agents connect

(written by GPT 5.5 in codex)
it appears to use a single active connection to the Godot editor bridge. When another MCP server instance connects to the same Godot editor, the previous instance becomes permanently unusable in its host session and reports:

```text
Error: Not connected to Godot
Status: Another MCP server connected and replaced this one
Suggestion: This server is no longer active. Restart it or close this session.

This is especially easy to trigger in agent workflows where sub

Read the thread · 2026-06-06 · closed · external user · 0 comments

The remaining reports are on the project's issue tracker.