Skip to main content
Glama
KyodanCFG

trenchbroom-mcp

by KyodanCFG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to trenchbroom-mcp

No user-submitted related servers found.

    Related Servers

    • h2mcp

      Nnamllit1
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
      -

    • zandronum-mcp

      rc4l
      A
      license
      C
      quality
      A
      maintenance
      Enables AI assistants to interact with the Zandronum game engine for development, including running commands, spawning actors, and loading maps.
      55
      18 npm
      3
      MIT

    • GameMaker MCP Server

      jhalek90
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to edit GameMaker projects, compile with GameMaker's own toolchain, and live-connect to a running game to inspect and steer it.
      MIT

    • OmniMod MCP

      Mcamento8
      F
      license
      B
      quality
      B
      maintenance
      Connects any AI agent to a live OmniMod game, enabling professional map building and Forge 1.20.1 mod authoring through 51 tools that translate modern block names, generate shapes, scaffold mods, inspect JARs, and bridge to the game over HTTP.
      51
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 17 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources