Skip to main content
Glama
IRSofka Workstation MCP

IRSofka Workstation MCP

by irsjofka-alt

Related Servers

Alternatives to IRSofka Workstation MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      D
      quality
      C
      maintenance
      Enables AI clients to control and inspect a Unity Editor through MCP tools for scene and play-mode operations, logs, screenshots, assertions, Lua execution, UI interaction, world observation, and bridge management; advanced UI/Lua/world features require project-specific adapters.
      41
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to operate the Unreal Editor via MCP: reading, creating, and editing blueprints at the node level, authoring materials and UMG widgets, auditing projects, and verifying runtime behavior in PIE with read-back checks.
      34
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    TDQS

    B3.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a clearly distinct domain: world actors, blueprints, materials, media, viewport vision, pipeline orchestration, and bridge status. The only possible overlap is ue_pipeline invoking operations from other tools, but its ordered-multi-step purpose is explicitly different from direct domain calls.

    Naming Consistency5/5

    All tools follow a consistent ue_<domain> naming pattern with lowercase snake_case-like names. The convention is predictable and readable across the entire set.

    Tool Count5/5

    Seven tools is well within the ideal range and matches the server's domain-grouped design. Each tool represents a coherent editor subsystem rather than an arbitrary or redundant operation.

    Completeness3/5

    The surface covers many major editor areas, but there are notable lifecycle gaps such as blueprint component/event authoring, material deletion or graph editing, and sequencer keyframe editing. These gaps are workable in some cases but will likely cause agent dead ends for common Unreal workflows.