Roslyn 增强的 C# 异常遥测数据，用于 Godot 引擎，通过 MCP 暴露。

---

什么是威克？

当 Godot C# 游戏崩溃时，你的 AI 助手会看到原始栈轨迹，并花费 8+ 回合要求你打开文件。Wick 捕捉该异常，并用 Roslyn 驱动的源上下文（实际方法体、调用链、近期日志、场景状态）丰富它，并在一次调用中将完整画面交给 AI。诊断只需一回合，而非十回合。

Wick 有什么不同？

其他 Godot MCP 服务器（如优秀的 GoPeak）则专注于场景操作和 GDScript 工具。Wick 专注于 C#/.NET 开发者体验：

• Roslyn 增强的异常遥测——用调用方法体、周围源行、包围类型和调用链丰富的 stderr 捕获的 C# 异常。其他 Godot MCP 服务器都不支持此功能。
• 进程中异常捕获 ——可选的 Wick.Runtime NuGet 伴随工具捕获 TaskScheduler.UnobservedTaskException 和 stderr 无法看到的异步异常。
• 带源上下文的构建诊断——dotnet构建错误通过与运行时例外相同的流水线，通过与运行时例外相同的流水线，通过Roslyn源上下文丰富。

Wick

Roslyn-enriched C# exception telemetry for Godot Engine, exposed over MCP.

---

What is Wick?

When a Godot C# game crashes, your AI assistant sees a raw stack trace and spends 8+ turns asking you to open files. Wick captures that exception, enriches it with Roslyn-powered source context (the actual method body, caller chain, recent logs, scene state), and hands the full picture to the AI in one call. One turn to diagnosis instead of ten.

What makes Wick different?

Other Godot MCP servers (like the excellent GoPeak) focus on scene manipulation and GDScript tooling. Wick focuses on the C#/.NET developer experience:

• Roslyn-enriched exception telemetry – stderr-captured C# exceptions enriched with the calling method body, surrounding source lines, enclosing type, and caller chain. No other Godot MCP server does this.
• In-process exception capture – optional Wick.Runtime NuGet companion catches TaskScheduler.UnobservedTaskException and async exceptions that stderr can’t see.
• Build diagnostics with source context – dotnet build errors enriched with Roslyn source context through the same pipeline as runtime exceptions.
• C# analysis tools – find symbol, find references, member signatures via Roslyn workspace.
• 5-pillar tool group system – activate only what you need: core, runtime, csharp, build, scene.

Getting Started

Prerequisites

• .NET 10 SDK (10.0.201 or later)
• Godot 4.6.1+ with .NET/Mono support

Installation

Wick has two parts: a Godot-side bridge addon (/addons/wick/) and the .NET MCP server.

Godot bridge — install via the Godot Asset Library in-editor (recommended), or copy /addons/wick/ into your project manually.

MCP server — clone and build:

git clone https://github.com/buildepicshit/Wick.git
cd Wick
dotnet build Wick.slnx --configuration Release -maxcpucount:1

MCP Configuration

Add Wick to your AI coding assistant’s MCP configuration:

{
  "mcpServers": {
    "wick": {
      "command": "dotnet",
      "args": ["run", "--project", "path/to/Wick/src/Wick.Server"],
      "env": {
        "WICK_GROUPS": "core,runtime,csharp,build",
        "WICK_GODOT_BIN": "/path/to/godot",
        "WICK_PROJECT_PATH": "/path/to/your/godot-project"
      }
    }
  }
}

Tool Groups

Activate tool pillars via WICK_GROUPS env var or --groups CLI flag: