Unity Editor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGGING | No | Enable logging to the terminal | false |
| UNITY_PORT | No | The port number for the WebSocket server connecting to the Unity Editor | 8080 |
| LOGGING_FILE | No | Enable logging to a log.txt file | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_menu_itemC | Executes a Unity menu item by path |
| select_objectC | Sets the selected object in the Unity editor by path or ID |
| package_managerC | Manages packages in the Unity Package Manager |
| run_testsC | Runs Unity's Test Runner tests |
| notify_messageC | Sends a message to the Unity console |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_menu_items | List of available menu items in Unity to execute |
| get_console_logs | Retrieve all logs from the Unity console |
| get_hierarchy | Retrieve all game objects in the Unity loaded scenes with their active state |
| get_packages | Retrieve all packages from the Unity Package Manager |
| get_assets | Retrieve assets from the Unity Asset Database |
| get_tests |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose targeting different Unity Editor functionalities: executing menu items, sending console messages, managing packages, running tests, and selecting objects. There is no overlap or ambiguity in their intended uses.
The tool names follow a consistent snake_case pattern with descriptive verb_noun combinations (e.g., execute_menu_item, notify_message). However, 'package_manager' deviates slightly by using a noun-only name instead of a verb_noun structure, but overall the naming is highly readable and predictable.
With 5 tools, the server is well-scoped for its purpose of interacting with the Unity Editor. Each tool serves a specific, essential function, and there are no extraneous or redundant tools, making the count appropriate for the domain.
The toolset covers key Unity Editor operations like executing commands, messaging, package management, testing, and object selection. However, there are notable gaps for a full editor integration, such as creating or modifying assets, building projects, or accessing scene hierarchies, which limits comprehensive workflow coverage.