WkMCP — an MCP server for Cyberpunk 2077 modding

An MCP (Model Context Protocol) server that exposes WolvenKit’s modding CLI (cp77tools) as 168 tools an agent (Claude) can call — so you steer Cyberpunk 2077 modding from a chat window without writing code: read and edit game files, query and patch the TweakDB, create/pack/install mods, export meshes and textures, lint REDscript, diagnose a broken install, and even drive a running game live.

Status: stable v2.0.0 · Windows. Built on the official ModelContextProtocol SDK 1.4.0 and WolvenKit 8.18.0; validated end-to-end on Windows 11 with a real Cyberpunk 2077 install.

Highlights

• Read & write game files — extract from archives, convert CR2W ↔ JSON, export meshes / textures / animations / audio.
• TweakDB editing — query tweakdb.bin, describe records, generate / validate / install .tweak (TweakXL).
• Create, pack & install mods — .archive mods, REDmods, REDscript, ArchiveXL items, localization.
• Diagnostics — mod_doctor (frameworks health), lint_mod, detect_conflicts, log analysis, conflict bisection.
• REDscript lint — a real grammar parser, line:column errors (0 false positives on 1374 real .reds).
• Live in-game bridge — 36 live_* tools to drive a running game (Lua, state, spawn, teleport, weather, in-memory TweakDB, event observation).
• Scenes — inspect, graph, validate, translate and edit .scene (quest/dialogue) files headlessly: catch broken dialogue graphs and edit subtitles without the scene editor.
• Structured JSON — every tool returns { ok, status, summary, produced, warnings, errors, log }, reliable for an agent to parse.

Quickstart (Windows, ~5 min)

1. Prerequisites. Windows 10/11, the .NET 8 SDK (), the WolvenKit CLI (dotnet tool install -g WolvenKit.CLI), and Cyberpunk 2077 installed (its root folder is written `` below).
2. Build — the daemon first (its build deploys kraken.dll and DirectXTexNet.dll), then the server:

   dotnet build src\WkDaemon
   dotnet build src\WkMcp
   

   The server is at src\WkMcp\bin\Debug\net8.0\WkMcp.dll.
3. Wire it to Claude Desktop — edit %APPDATA%\Claude\claude_desktop_config.json:

   {
     "mcpServers": {
       "wolvenkit": {
         "command": "dotnet",
         "args": ["C:\\path\\to\\wkmcp\\src\\WkMcp\\bin\\Debug\\net8.0\\WkMcp.dll"]
       }
     }
   }
   

   Restart Claude Desktop. (Claude Code: claude mcp add wolvenkit -s user -- dotnet "C:\path\to\...\WkMcp.dll".)
4. Verify. Ask Claude to call wk_status — it returns the CLI version and the cache/metrics stats, confirming the server is live.
5. Call a tool. Try find_in_archives with archivesFolder = \archive\pc\content and pattern = *player*.ent. Every tool returns the same structured shape: