Sauerbraten MCP
Related Servers
Alternatives to Sauerbraten MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables inspecting J.A.C.K. Map Editor documents and live selections, and previewing or applying limited native brush and entity edits through a stdio MCP client.MIT
- AlicenseNot gradedqualityCmaintenanceLets an AI client inspect and edit CRYENGINE 5.7.1 projects by driving the Sandbox editor through a local TCP bridge, covering objects, levels, terrain, vegetation, console, Python and screenshots. It also validates project data against what the engine actually loads and supplies engine catalogs, background jobs and a knowledge base of measured engine traps.MIT
- AlicenseNot gradedqualityCmaintenanceEnables any MCP client to drive the Fortnite map editor through typed, safety-validated tools — placing and tagging props, renaming assets with Verse-reference pre-flight, authoring prefabs, exporting textures for visual identification, and searching the project's Verse API digests. An in-editor listener executes the operations on the editor's main thread over HTTP.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding tools to connect and authorize local game projects, then drive source edits, validation, preview, version saving, and mode-based creation workflows.Apache 2.0
- AlicenseAqualityCmaintenanceConnects an MCP client to a running Serious Editor 2017 / Serious Sam Fusion instance through a local Lua bridge, enabling package and entry inspection, log reading, editor diagnostics, and previewed/undoable entity property edits on a captured selection.14MIT
- AlicenseNot gradedqualityCmaintenanceEnables full control of the Godot engine from any MCP client through three layers: headless project, scene, script, settings and export operations, live editor edits that remain undoable, and inspection of a running game with input injection, frame-stepped digests and screenshots. Each layer also exposes an arbitrary-GDScript escape hatch so unanticipated tasks can still be performed.MIT
TDQS
Scored across 22 tools
Each tool targets a distinct resource+action: entities (create/update/delete/list), geometry (fill/face_set/vertex_set), textures (catalog/apply), maps (new/open/save_as/catalog), and history (undo/redo). Minor possible confusion between material_apply vs texture_apply and between the three *_catalog tools, but descriptions clearly scope them to different domains. The three geometry mutation tools are clearly separated by the type of shape manipulation.
Dominant pattern is noun_verb (entity_create, geometry_fill, texture_apply, map_open), applied consistently across domains. A few outliers like editor_state, operation_status, and map_save_as are noun_noun or verb-phrase forms rather than the strict verb at end, but still readable and predictable.
22 tools is above the ideal 3-15 band but justified by a rich 3D map editor spanning entities, geometry, textures, maps, camera, and history. Each domain contributes a small, purposeful cluster rather than redundant tools, so the count feels earned though slightly heavy.
Covers a strong lifecycle: map new/open/save/catalog, entity CRUD+list, geometry mutation, texture catalog/apply, material apply, camera, history undo/redo, operation_status, and region_read for readback. Minor gaps exist (no material catalog listing, no explicit entity get-by-ref beyond entity_list), but agents can work around these.