Skip to main content
Glama
YElwiddi

Warcraft 3 MCP Server

by YElwiddi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Warcraft 3 MCP Server

No user-submitted related servers found.

    Related Servers

    • giants-editor-mcp

      0h-MARVVV
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to drive a live GIANTS Editor 10.x (FS25) session with 59 tools for terrain editing, field creation, asset placement, map audits, and more through natural language.
      1
      MIT

    • Portals MCP

      busportals
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables Claude to design and build interactive 3D games within the Portals virtual platform through direct API integration. It facilitates automated asset placement, interaction logic configuration, and quest management using natural language commands.
      4
      -

    • UEMCP

      ATDev-Inc
      A
      license
      B
      quality
      C
      maintenance
      Enables Claude to control Unreal Engine 5 editor, spawn actors, build materials, author Blueprints, and more, with zero plugin installation.
      31
      MIT

    • blender-mcp

      Vertiiii
      A
      license
      A
      quality
      C
      maintenance
      Connects Blender 3D modeling software with Claude AI, enabling natural language control of 3D modeling and scene manipulation tasks.
      17
      4
      MIT

    • Atelier

      lebac-svg
      A
      license
      Not graded
      quality
      A
      maintenance
      Converts spoken descriptions into standards-compliant floor plans and furnished 3D models, enabling real-time collaborative editing through a live browser editor with Claude AI.
      3 npm
      Apache 2.0
    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

    A3.6/5.0

    Scored across 35 tools

    Disambiguation5/5

    Each tool targets a unique resource and action (e.g., add_camera, delete_unit, read_terrain). Overlaps like list_doodads vs read_placements are clarified by descriptions focusing on different use cases (listing for modification vs comprehensive snapshot). No two tools serve the same purpose.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with the 'wc3_' prefix (e.g., add_camera, delete_doodad, read_script). No mixing of conventions (camelCase, etc.), making the pattern predictable and easy to understand.

    Tool Count2/5

    With 35 tools, this exceeds the 25+ threshold for 'too many' per the rubric. While the complex domain of Warcraft III map editing justifies many tools, the count is still high and could be streamlined. Some tools could be merged (e.g., list_* and read_* could be combined).

    Completeness4/5

    The tool set covers most major aspects: CRUD for units, doodads, regions, cameras, objects; script and trigger management; file handling; and testing/editor integration. Minor gaps exist (no terrain modification, no import management, no map info update), but these do not break core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources