Godot MCP Runtime vs Wavedash

In-depth architectural comparison of the Godot MCP Runtime and Wavedash MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Godot MCP Runtime when:

• You need dedicated capabilities in the Gaming domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: BRIDGE_PORT.
• Primary tools included: Headless editing of scenes, nodes, scripts, and signals, Runtime bridge for screenshots and input simulation, UI discovery of visible Control nodes with metadata.

Explore Godot MCP Runtime Details

Choose Wavedash when:

• You need dedicated capabilities in the Gaming domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Wavedash Details

Feature & Specification Comparison

Specification	Godot MCP Runtime Erodenn Gaming	Wavedash Gaming
Summary	MCP server for Godot 4.x with runtime control via injected UDP bridge: input simulation, screenshots, UI discovery, and live GDScript execution while the game is running.	Wavedash docs and workflow guidance for building and publishing browser games.
Category & Scope	Gaming

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "erodenn-godot-mcp-runtime": {
      "command": "npx",
      "args": [
        "-y",
        "and"
      ],
      "env": {
        "BRIDGE_PORT": "YOUR_BRIDGE_PORT_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "wavedash": {
      "command": "npx",
      "args": [
        "-y",
        "wavedash"
      ]
    }
  }
}

Related MCP Server Comparisons