Wick MCP server
Provides Roslyn-enriched C# exception telemetry and source context for Godot Engine to help AI assistants diagnose game crashes.
Also known as buildepicshit/Wick
- Stars
- 22
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Aug 17, 2026
- License
- MIT
What is Wick MCP?
Wick provides Roslyn-enriched C# exception telemetry and source context for Godot Engine to help AI assistants diagnose game crashes.
Summary generated from the project's README
About Wick MCP server
Wick provides Roslyn-enriched C# exception telemetry for developers using the Godot Engine. It is designed to help AI assistants diagnose game crashes by providing full source context, including method bodies and caller chains, instead of just raw stack traces. This server runs as an external process and communicates with Godot via TCP bridges, while the AI client connects through stdio.
Users must install a Godot bridge addon and configure the MCP server with environment variables like WICK_GODOT_BIN and WICK_PROJECT_PATH. For advanced debugging, the Wick.Runtime NuGet package can be added to a project to capture async exceptions and unobserved task errors. The system uses a five-pillar tool group system, allowing developers to enable specific capabilities such as core, runtime, csharp, build, or scene tools via the WICK_GROUPS setting.
What you can do with it
- 1Diagnose C# runtime crashesAsk the AI to explain a crash using enriched telemetry that includes the surrounding source lines and enclosing type.
- 2Debug build errorsProvide the AI with dotnet build errors that include specific source context for faster fixing.
- 3Capture asynchronous exceptionsUse the runtime companion to catch exceptions occurring in tasks that standard stderr cannot detect.
Written from the project's README. Every use case is checked against a quote from it.
Configuration
WICK_GODOT_BINWICK_GROUPSWICK_PROJECT_PATH
| Name | Description | |
|---|---|---|
| WICK_GODOT_BIN | — | |
| WICK_GROUPS | — | |
| WICK_PROJECT_PATH | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablebuildepicshit/wick is public and reachablegithub.com/buildepicshit/wick ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-08-17github.com/buildepicshit/wick ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubWick
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 |
|---|---|---|
| core | GDScript tools, scene parsing, GDScript LSP, introspection | Always on |
| runtime | Exception pipeline, game launch/stop, log tail, runtime_diagnose | Opt-in |
| csharp | Roslyn analysis, find symbol, find references, member signatures | Opt-in |
| build | dotnet build/test/clean, NuGet management, build_diagnose | Opt-in |
| scene | Scene create/modify via headless Godot dispatch | Opt-in |
Example: WICK_GROUPS=core,runtime,csharp,build or --groups=all.
Optional: Wick.Runtime Companion
For in-process exception capture (async exceptions, TaskScheduler.UnobservedTaskException) and live scene-tree queries, add the Wick.Runtime NuGet companion to your Godot C# project:
dotnet add package Wick.Runtime
Wire both Install() and Tick() into your game's entry point — both are required:
using Wick.Runtime;
public partial class Main : Node
{
public override void _Ready() => WickRuntime.Install();
public override void _Process(double delta) => WickRuntime.Tick();
}
If your in-process bridge tools (
runtime_query_scene_tree, etc.) hang forever, you forgotTick().Install()alone covers exception capture, but live RPC handlers needTick()to drain the main-thread dispatcher. Seedocs/getting-started.mdand the package README for the full story.
Architecture
Wick runs as an external process -- it does NOT run inside Godot. Communication:
- stdio -- MCP protocol to the AI client
- TCP 6505 -- editor bridge (Godot plugin to Wick server)
- TCP 7777 -- runtime bridge (running game to Wick server)
- TCP 7878 -- Wick.Runtime companion bridge (in-process to Wick server)
This architecture lets the Wick server and provider projects target .NET 10
while the optional in-process Wick.Runtime companion stays on net8.0 for
Godot 4.6.1's current stable .NET runtime.
Attribution
Wick is a clean-room reimplementation inspired by GoPeak (MIT License, (c) 2025 Solomon Elias / HaD0Yun). See ATTRIBUTION.md for detailed credits.
Contributing
We welcome contributions! Please read CONTRIBUTING.md before submitting a PR.
Demo
Clone the repo and open docs/demo/player.html in a browser to watch the demo, or play the cast file directly:
asciinema play docs/demo/wick-demo.cast
License
Wick MCP questions
How does Wick improve AI debugging in Godot?
Wick captures C# exceptions and enriches them with Roslyn-powered source context like method bodies and caller chains, allowing the AI to diagnose issues in one turn instead of many.
What are the prerequisites for using Wick?
You need .NET 10 SDK (version 10.0.201 or later) and Godot 4.6.1 or higher with .NET/Mono support.
Can Wick capture async exceptions?
Yes, by using the optional Wick.Runtime NuGet companion, you can capture TaskScheduler.UnobservedTaskException and other async exceptions.