L4D2-HSMCP
Related Servers
Alternatives to L4D2-HSMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that lets AI agents see and edit maps in Valve Hammer Editor: Source 1 Hammer, Hammer++, Strata, Source 2 (read)40MIT
- 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-
- FlicenseAqualityCmaintenanceEnables AI agents to edit Quake-format .map files and see their changes appear live in TrenchBroom, with tools for reading, editing, previewing, compiling, and launching maps.172-
- AlicenseAqualityDmaintenanceCustom MCP server that lets AI control Autodesk Maya 2022+ directly, using code execution and self-discovery rather than hundreds of predefined tools. Includes structured tools for Unreal Engine asset preparation, validation, and FBX export.16MIT
- AlicenseBqualityCmaintenanceAn MCP server that lets an AI agent drive Unreal Engine 5: create projects, import assets, build levels and Blueprints, configure replication, compile C++, run Play In Editor and package the game.100187 PyPI6MIT
- AlicenseAqualityBmaintenanceEnables AI agents to set up and use a private local Minecraft test server, build and validate maps block by block, and export creations as schematics for any server.24496 npmMIT
TDQS
Scored across 80 tools
Despite 80 tools, most have sharply distinct purposes and the descriptions actively cross-reference near-neighbours (read_sightlines vs read_vmf_sightlines, read_vmf vs read_entity_report, read_map_geometry vs read_map_report, read_pakfile vs run_pakfile_extract). A few pairs still require careful reading to separate — read_vmf_lint vs check_vmf_rules vs validate_io, run_pack vs run_vpk_pack — but the descriptions resolve them rather than leaving them ambiguous.
Nearly everything follows a verb_noun pattern with a small verb vocabulary (read_, write_, run_, check_, set_, measure_, render_, delete_, plus brush verbs like clip_solids, hollow_solids, sew_displacements). The only real outlier is the bare noun 'health', and a couple of noun-ish actions (group_solids, align_faces) that still read clearly.
80 tools for a map-authoring toolchain is far past what an agent can hold in view at once, and many are narrow single-purpose helpers (set_cordon, set_smoothing_groups, align_faces, sew_displacements). The domain is genuinely broad — VMF editing, compiling, VPK, nav, materials, rendering — but several are grouped by sub-feature rather than by coherent task, which inflates the surface.
The lifecycle is covered end to end: campaign read/write/check, VMF creation through brush/displacement/entity/texture editing and organisation, linting, compilation, leak triage, packing, nav, cubemaps, rendering, and play-testing. Even verification has its own tools (read_vmf_solids as an independent checker, read_map_report as a stopping condition), so few obvious dead ends remain.