DeadlockMCP
Related Servers
Alternatives to DeadlockMCP
No user-submitted related servers found.
Related Servers
- 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 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.5 npmGPL 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
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to work inside a live Unreal Editor for Fortnite session: write and compile Verse, place and wire Creative devices, edit Scene Graph entities, manipulate actors and assets, take screenshots, run playtests, and read editor logs via MCP.MIT
- AlicenseNot gradedqualityBmaintenanceEnables debugging web pages in Chrome through a stdio MCP interface, including performance traces, network and console inspection, snapshots, screenshots, emulation, and page input by element UID.79 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to inspect, edit, and validate Arma Reforger addons in Workbench, including Enforce Script source, prefab/world files, resource GUIDs, and Workbench startup diagnostics.MIT
TDQS
Scored across 24 tools
Several tools converge on the same job of styling live panels: css_apply (inline sheets), layout_live_edit (persistent inline-style sheets via an edited stylesheet), xml_load's css parameter, and compile_source (permanent overrides), while css_clear and layout_live_revert both undo. The descriptions do explain the differences, and inspection tools (panel_find, panel_tree, js_eval) are distinct, but choosing the right styling path requires reading carefully. bridge_uninstall, remove_override and panel_delete are also easy to mix up at a glance despite targeting different things (bridge files, compiled overrides, panels).
Everything is snake_case, but the verb/noun ordering is mixed: verb_noun (launch_game, compile_source, list_overrides, remove_override) alongside noun_verb (bridge_install, css_apply, css_clear, panel_find, layout_live_edit) and bare nouns (status, setup, screenshot, console_log, ui_files). The prefix grouping (panel_*, css_*, bridge_*, *_override) gives some structure, but the set is not a single predictable pattern.
24 tools is heavy, but the domain — UI inspection, live CSS manipulation, compilation, bridge management, and mod packaging — genuinely spans that surface, and nearly every tool has a distinct role. A few (layout_live_revert, css_clear overlaps) could arguably be folded together to trim the set.
The lifecycle is well covered end to end: setup and status, launching/quitting, decompiling and inspecting shipped UI, live panel discovery/manipulation, CSS application and clearing, compilation into permanent overrides with listing/removal, and exporting/mounting mods. Given the description indicates input simulation or log tailing beyond a fixed console.log read, there are no obvious dead ends.