Server facts
MCP Unity Editor
Project
- Author
- CoderGamester
- Repository
- github.com/CoderGamester/mcp-unity
- License
- MIT
- Category
- Games & 3D
Tech
- Runtime / language
- c#C# and TypeScript
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 1,935
- Last commit
- Data as of
Tags
- Editor Automation
- Game Development
- Scene Management
- Test Runner
- Unity
Overview
MCP Unity Editor connects AI development assistants to operations inside Unity projects. A Unity package communicates with a Node.js MCP server, allowing clients to work with scenes, GameObjects, components, materials, and assets. The toolset includes creating and saving scenes, duplicating or reparenting objects, changing transforms, and modifying component fields. It also supports package installation, script recompilation, console inspection, and Unity Test Runner execution. Batch operations can combine multiple tool requests with optional rollback behavior, reducing the need for separate calls during repetitive editing.
The integration supplies more than tools. Resources expose scene hierarchy, menu items, packages, assets, logs, and tests, while prompts guide GameObject workflows and dashboard access. A Unity dashboard MCP App is available in supported VS Code versions, and play-mode tools can start, pause, stop, or step the editor. Requirements include Unity 6 or later and Node.js 18 or later; npm 9 or later is listed for debugging. Installation uses Unity Package Manager with the repository's Git URL, followed by configuration in the MCP Unity server window. Global client configuration uses absolute paths, while project configuration uses relative paths intended for team sharing. The supplied README excerpt ends during that setup sequence, so it does not provide the final server launch command despite documenting installation and configuration concepts.
Install & configure
Requirements
- Unity 6+
- Node.js 18+
- The MCP Unity package installed through Unity Package Manager
- An MCP-compatible client
No install command stated in the README — see repo.
A final runnable server launch command is not stated in the provided README excerpt. Install the package from https://github.com/CoderGamester/mcp-unity.git, then use Tools > MCP Unity > Server Window for client configuration. npm 9+ is listed for debugging.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Claude Desktop setup guideConfig file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Cursor setup guideConfig file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the VS Code setup guideConfig file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Windsurf setup guideConfig file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Claude Code setup guideExamples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
Source: repository README. Tool descriptions are a documented snapshot, not a live capability check.
| Tool | What it does |
|---|---|
| execute_menu_item | Invoke an editor menu action exposed through Unity's MenuItem attribute. |
| select_gameobject | Select an object using its hierarchy path or instance identifier. |
| update_gameobject | Change core object settings, or create the object when it is missing. |
| update_component | Change component fields or attach a missing component to an object. |
| add_package | Install a package through Unity Package Manager. |
| run_tests | Execute tests through Unity Test Runner. |
| send_console_log | Write a log message into the Unity console. |
| add_asset_to_scene | Place an AssetDatabase asset into the active scene. |
| create_prefab | Create a prefab with optional script and serialized field values. |
| create_scene | Create a scene asset at a chosen path. |
| load_scene | Open a scene by path or name, optionally loading additively. |
| delete_scene | Delete a scene asset and remove its Build Settings entry. |
| get_gameobject | Inspect an object's details and attached components. |
| get_console_logs | Retrieve editor console output with pagination. |
| recompile_scripts | Trigger recompilation of project scripts. |
| save_scene | Save the active scene, optionally to a new location. |
| get_scene_info | Inspect active and loaded scenes, including path and unsaved-change state. |
| unload_scene | Remove a loaded scene from the hierarchy without deleting its asset. |
| duplicate_gameobject | Copy an object with optional name and parent changes. |
| delete_gameobject | Remove an object from a scene. |
| reparent_gameobject | Move an object under a different hierarchy parent. |
| move_gameobject | Change an object's position in local or world coordinates. |
| rotate_gameobject | Change local or world orientation using Euler angles or a quaternion. |
| scale_gameobject | Change an object's local scale. |
| set_transform | Update position, rotation, and scale together. |
| create_material | Create and save a material using a specified shader. |
| assign_material | Apply a material to an object's Renderer component. |
| modify_material | Change an existing material's colors, numeric properties, or textures. |
| get_material_info | Inspect a material's shader and properties. |
| batch_execute | Run multiple operations in one request with optional rollback on failure. |
| show_unity_dashboard | Open the Unity dashboard MCP App in a supported VS Code client. |
| get_play_mode_status | Inspect whether the Unity editor is playing or paused. |
| set_play_mode_status | Start, pause, stop, or step Unity's play mode. |
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
Use cases
- Create scenes, prefabs, and GameObjects from an assistant.
- Adjust transforms, component fields, and material properties.
- Run Unity tests and inspect editor console errors.
- Batch repetitive scene edits with optional rollback.
- Share project-relative MCP configuration across a development team.
Strengths
- Provides tools, resources, prompts, and an optional dashboard app.
- Covers scene editing alongside testing and console inspection.
- Supports batching and portable project-level configuration.
Limitations
- Requires Unity 6+ and Node.js 18+.
- The dashboard MCP App requires VS Code 1.109+ according to the README.
- A final server launch command is not stated in the supplied README excerpt.
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.
