Skip to main content
Glama
Shonas301

headless-unity-mcp

by Shonas301
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to headless-unity-mcp

No user-submitted related servers found.

    Related Servers

    • ProjectM QA MCP

      chdnl0420-svg
      F
      license
      Not graded
      quality
      B
      maintenance
      A Unity Editor command bridge that uses JSON files under .codex/unity-commands for request/response, enabling tools to check Unity status, execute editor commands, parse test results, and capture screenshots.
      -

    • ShiryuUnityMCP

      Shiryu-Studios-LLC
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables supported AI clients to connect to and automate the Unity Editor, covering scene and GameObject manipulation, asset and material operations, script creation and validation, testing, builds, screenshots, and editor-state inspection. It supports HTTP and stdio transports and ships client configuration helpers for Unity 2021.3+ on Windows, Linux, and macOS.
      MIT

    • UnityMCP

      zloybest
      F
      license
      Not graded
      quality
      B
      maintenance
      Local Streamable HTTP MCP server exposing Unity Editor inspection, authoring, testing, profiling, play-mode, and build tools.
      -

    • dcc-mcp-unity

      dcc-mcp
      A
      license
      Not graded
      quality
      A
      maintenance
      Unity Editor adapter for the DCC MCP ecosystem, providing tools to inspect and modify Unity projects, scenes, builds, and diagnostics through a WebSocket bridge.
      28 PyPI
      MIT

    • mcp-server-unity

      handi425
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Claude to interact with Unity projects programmatically, supporting project management, asset creation, and build automation.
      1
      MIT
    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.9/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a distinct Unity operation: screenshot, lock status, build, list targets, compile, test, and scene generation. Build vs compile are clearly differentiated by their descriptions, and no two tools appear to serve the same purpose.

    Naming Consistency4/5

    All tools share a consistent 'unity_' prefix, but the action words mix verbs (build, compile, test) with nouns (shot, status, targets, scene). This is mostly predictable but deviates from a pure verb_noun pattern.

    Tool Count5/5

    With 7 tools, the server is well-scoped for a Unity CI/headless workflow. Each tool covers a specific need without redundancy, and the count is well within the ideal 3-15 range.

    Completeness4/5

    The tool surface covers the core lifecycle: build, compile, test, screenshot, and scene generation, plus target listing and lock status. Minor gaps like explicit lock release or raw log retrieval are workarounds, but the main workflows are complete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources