trenchbroom-mcp
Related Servers
Alternatives to trenchbroom-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI clients to create, inspect, edit, and deploy Counter-Strike 2 maps and addons by working with Hammer map files, addon source files, Valve's resource compiler, and Workshop Tools locally.1-
- AlicenseAqualityBmaintenanceAn MCP server and agent skill that let an AI build Left 4 Dead 2 maps, campaigns, VScripts and addons by reading and splicing VMF/BSP files by offset, linting against the game's FGD, running the stock or Tools++ compile chain, generating nav meshes, and packing VPKs. It also offers offline leak, clearance, trace and render checks so geometry can be validated before spending a compile.80GPL 3.0
- AlicenseNot gradedqualityBmaintenanceMCP server that lets AI agents see and edit maps in Valve Hammer Editor: Source 1 Hammer, Hammer++, Strata, Source 2 (read)40MIT
- AlicenseBqualityBmaintenanceEnables live editing of levels in a running Sauerbraten (Cube 2) game through typed tools for geometry, textures, entities, history, camera capture, and map persistence over a private native bridge.22zlib
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read, audit, and byte-faithfully edit Warcraft III .w3x and .w3m maps while preserving untouched file bytes, with tools for metadata, objects, terrain, sounds, cameras, triggers, and more.4Apache 2.0
- FlicenseAqualityBmaintenanceEnables AI agents to control the DX12 Engine editor for game development, including scene editing, entity manipulation, and playback testing via natural language commands.73-
TDQS
Scored across 17 tools
Each tool targets a distinct operation: map info, undo, preview, two separate compilers, FGD queries, entity CRUD, brush add/delete, and translation. No two tools have overlapping purposes; even compile_map and compile_shogo_map are clearly differentiated by toolchain.
Most tools follow a verb_noun pattern in snake_case (list_entities, add_entity, delete_brush, translate_entity). Two tools (fgd_classes, fgd_class) use a noun-first structure, but the pattern is still predictable and all names are lowercase with underscores, so minor deviation only.
With 17 tools, the count is slightly above the typical 3-15 range, but each tool serves a distinct need for map editing, compilation, and FGD introspection. The scope is broad but well-justified, making the count reasonable.
The tool surface covers the full lifecycle: map analysis, editing (add/update/delete entities and brushes), transformation (translate), undo/backups, preview rendering, compilation for two engines, and FGD entity lookups. No significant gaps for the stated purpose of TrenchBroom map manipulation.