L2 Modding MCP
Related Servers
Alternatives to L2 Modding MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that enables natural language listing, unpacking, and exporting of Unreal Engine game resources via umodel, including AES-encrypted pak support.137 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server that integrates with Unreal Engine to read and modify complex editor objects using SAL, providing tools for queries, patches, schema discovery, and editor control.13MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server for AI-driven Blender↔Unreal Engine bridge, providing 62 tools for 3D modeling, scene validation, and asset transfer across both engines.MIT
- AlicenseBqualityAmaintenanceAn 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.10096 PyPI4MIT
- AlicenseNot gradedqualityAmaintenanceOpen-source, engine-agnostic MCP server shared by Unity-MCP, Godot-MCP, and Unreal-MCP.14Apache 2.0
- FlicenseNot gradedqualityBmaintenanceMCP server for procedural material generation and inspection via a deterministic Texture DSL, exposing tools to list, validate, render, and multiscale-inspect materials.-
TDQS
Scored across 18 tools
Each tool targets a distinct operation on L2 package assets (listing, extracting, importing, generating, comparing). No overlapping purposes; even similar tools like l2_extract_texture and l2_extract_all_textures are clearly differentiated by scope.
All tools follow the 'l2_verb_noun' pattern consistently, using snake_case. Verbs like list, compare, extract, import, generate, create are predictably placed, making the set easy to navigate.
With 18 tools covering textures, meshes, animations, packages, and procedural generation, the count fits the modding domain well. Each tool serves a clear purpose without redundancy.
The toolset covers most modding workflows: texture and package management, mesh import/export, animation export, procedural generation. Minor gaps exist (e.g., no animation import/creation, no generic package creation for non-castle assets), but core operations are well-supported.