What is the key difference between Wick and Godot MCP?

Wick belongs to the Gaming category with local stdio execution, while Godot MCP belongs to the Gaming category with local stdio execution.

How do I install Wick or Godot MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Wick and Godot MCP free or paid?

Wick operates under a Free / Open Source model (No auth required). Godot MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Wick lists 6 tools with 5 views and 20 GitHub stars. Godot MCP lists 6 tools with 5 views and 5,550 GitHub stars.

Can I use both Wick and Godot MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Wick vs Godot MCP

In-depth architectural comparison of the Wick and Godot MCP 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.

At a Glance & Executive Verdict

Wick

Gaming · Local stdio

Quality: 48/100 (Fair) | Auth: No auth required

Godot MCP

Gaming · Local stdio

Quality: 59/100 (Good) | Auth: No auth required

Verdict Summary: Choose Wick if you need specialized Gaming tools running via a local process. Choose Godot MCP if your workspace requires Gaming integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Wick 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: WICK_GROUPS, WICK_GODOT_BIN, WICK_PROJECT_PATH.
Primary tools included: Roslyn-enriched exception telemetry, C# symbol and reference analysis, GDScript and scene tooling.

Explore Wick Details

Choose Godot MCP 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: GODOT_PATH, DEBUG.
Primary tools included: Godot editor and project execution control, Debug output and error retrieval, Project discovery and structural analysis.

Feature & Specification Comparison

Specification	Wick buildepicshit Gaming	Godot MCP Coding-Solo Gaming
Summary	⃣ 🏠 🍎 🪟 🐧 - Native C MCP server for Godot Engine — 53 tools across 5 pillars: Roslyn-enriched exception telemetry, scene tree inspection, C symbol navigation, MSBuild orchestration, and GDScript analysis. .NET 10, TCP JSON-RPC bridge, 219 tests.	A MCP server for interacting with the Godot game engine, providing tools for editing, running, debugging, and managing scenes in Godot projects.
Category & Scope

Tools & Capabilities Breakdown

Wick Tools (6)

Roslyn-enriched exception telemetry

C# symbol and reference analysis

GDScript and scene tooling

Runtime launch, logging, and diagnosis

MSBuild, test, clean, and NuGet operations

Configurable MCP tool groups

Godot MCP Tools (6)

Godot editor and project execution control

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).

Wick Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "buildepicshit-wick": {
      "command": "npx",
      "args": [
        "-y",
        "buildepicshit-wick"
      ],
      "env": {
        "WICK_GROUPS": "YOUR_WICK_GROUPS_HERE",
        "WICK_GODOT_BIN": "YOUR_WICK_GODOT_BIN_HERE",
        "WICK_PROJECT_PATH": "YOUR_WICK_PROJECT_PATH_HERE"
      }
    }
  }
}

Godot MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "coding-solo-godot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@coding-solo/godot-mcp"
      ],
      "env": {
        "GODOT_PATH": "YOUR_GODOT_PATH_HERE",
        "DEBUG": "YOUR_DEBUG_HERE"
      }
    }
  }
}

Frequently Asked Questions

Wick is categorized under Gaming and uses a local stdio subprocess. In contrast, Godot MCP belongs to Gaming using local stdio subprocess. Select Wick when you need capabilities focused on gaming and Godot MCP when you require tools for gaming.

More alternatives to Wick More alternatives to Godot MCP Gaming category hub