
buildepicshit/wick
Developer tools이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
Roslyn-enriched C# exception telemetry for Godot Engine, exposed over MCP
개요
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. Other Godot MCP servers (like the excellent GoPeak) focus on scene manipulation and GDScript tooling. Wick focuses on the C#/.NET developer experience: - -- 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. - -- optional Wick.Runtime NuGet companion catches TaskScheduler.UnobservedTaskException and async exceptions that stderr can't see. - -- dotnet build errors enriched with Roslyn source context through the same pipeline as runtime exceptions. - -- find symbol, find references, member signatures via Roslyn workspace.
README
원문 README의 일부입니다. 원문 보기.
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:
| Pillar | What it includes | Default |
|---|
설치
This server does not publish a one-line install command.
Open the repository installation guide MCP 초보자라면? mcpskill.org 가이드부터 시작하세요 →설정
{
"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"
}
}
}
}