Skip to main content
Glama
Vangardo

Unity MCP Efficient

by Vangardo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Unity MCP Efficient

No user-submitted related servers found.

    Related Servers

    • unity-biome-mcp

      german-krasnikov
      A
      license
      A
      quality
      A
      maintenance
      MCP server for controlling the Unity Editor from AI clients. 140+ tools for scenes, GameObjects, components, assets, Shader Graph, PlayTest DSL, screenshots with visual diff, batch operations with Undo rollback, and in-editor chat. Token-efficient plain-text protocol.
      36
      29
      MIT

    • SimpleMcpServer

      redcool
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents (like Claude Code, Cursor) to directly operate Unity scenes via MCP protocol, with tools for scene hierarchy, object creation/deletion, and transform modification.
      6 npm
      1
      ISC

    • unity-mcp-server

      Mishaadevv
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to inspect and modify a live Unity 6 Editor over stdio, handling scenes, GameObjects, components, scripts, prefabs, assets, console logs, and play-mode control. It also supports sandboxed C# execution and remote input hooks for AI-driven self-play and game-state snapshots.
      34
      51 npm
      MIT

    • Unity MCP Server

      wondeks
      A
      license
      Not graded
      quality
      B
      maintenance
      Allows MCP clients like Claude Desktop or Cursor to perform Unity Editor actions, including asset management, scene modification, and game mechanic testing.
      22
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct phase of interaction: discovery, execution, result retrieval, batching, semantic inspection, and visual verification. There is no meaningful overlap that would cause an agent to misselect between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: search_, call_, get_, batch_, inspect_, get_. This makes the set predictable and easy to navigate.

    Tool Count5/5

    Six tools is a well-scoped count for an efficiency-focused server. Each tool earns its place and the set avoids both bloat and thinness.

    Completeness4/5

    The surface covers the main lifecycle well: discover capabilities, execute operations, retrieve results, batch workflows, inspect Unity state, and verify visually. Minor gaps exist, such as no explicit cancellation or full listing tool, but search_capabilities and batch_operations cover most practical needs.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources