forge-mcp
Related Servers
Alternatives to forge-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to research game mods by searching documentation and definitions, inspecting dependencies and playsets, validating saved files with structural and Tiger checks, and preparing or editing mod content with preview and write controls. It also supports starting or previewing the game through a local stdio connection.8 npmGPL 3.0
- AlicenseNot gradedqualityDmaintenanceMCP server that gives Claude Code access to WolvenKit for Cyberpunk 2077 modding. Extract archives, convert game files to JSON, inspect meshes and textures, manage mods, and build mod projects — all from your terminal.3MIT
- AlicenseAqualityCmaintenanceGives MCP clients such as Claude Code and OpenCode a static-analysis toolbox for binaries, executables, DLLs, shared objects, and web-app code, covering file identification and hashing, string extraction, PE/ELF/Mach-O/WASM parsing, disassembly, Ghidra decompilation, YARA scanning, and JavaScript deobfuscation. All inspection is read-only and never executes the target.16MIT
- AlicenseCqualityDmaintenanceA comprehensive MCP server that provides AI assistants with tools for file system management, Git integration, and shell command execution. It features specialized code utilities for analysis, formatting, and linting to enhance development workflows within Claude Desktop.287MIT
- AlicenseBqualityCmaintenanceEnables an MCP-capable assistant to search and cite Metal Gear Solid V modding documentation, browse catalogued upstream source at pinned commits, and inspect file headers and hashes. It also stages copies of files into isolated job folders to run supported, separately installed archive, texture, language and animation converters, recording commands, logs and changed-file hashes for review.25GPL 3.0
- AlicenseBqualityBmaintenanceLets MCP clients browse vanilla data, add or override table rows, edit asset properties, check Blueprint symbols, and validate mods before packaging.21MIT
TDQS
Scored across 10 tools
Multiple actions are duplicated across tools: find_function lives in both inspect and search (pe), verify_signature appears in patch_code, validate, and rebuild, rebuild_offsets in both edit and rebuild, and validate in both rebuild and validate. check_dependencies even appears twice within diagnose under different modules. The module dispatch layers are coherent internally, but the cross-tool duplication means an agent can plausibly pick the wrong tool for the same operation.
All names are snake_case, verb-first, and readable (inspect, search, edit, rebuild, validate, export, diagnose, undo). Minor deviation: open_game and patch_code use verb_noun while the rest are bare verbs, though this actually helps signal they are the entry-point/utility tools.
Ten top-level tools is a sensible count for a game-modding forge. However, each tool is a mega-dispatcher bundling 2-9 actions, so the effective surface is much larger than 10 and some tools (inspect, edit) carry heavy action loads.
The surface covers a full modding lifecycle: open workspace, inspect formats (PE/APK/Unity/Unreal/tables/archives), search/diff, edit with snapshots, patch code, rebuild/repack, validate, export patch tables, diagnose, and undo. Minor gaps: no way to list/close workspaces or manage snapshots directly, and job log access only via export.