MCP Server for Unity
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| script_createC | Create a new C# script in Unity project |
| script_readC | Read a C# script from Unity project |
| script_deleteC | Delete a C# script from Unity project |
| script_apply_diffC | Apply a unified diff to a C# script |
| shader_createC | Create a new shader in Unity project |
| shader_readC | Read a shader from Unity project |
| shader_deleteC | Delete a shader from Unity project |
| project_infoB | Get comprehensive Unity project information including render pipeline details, project path, Unity version, and platform info |
| project_statusA | Check Unity MCP server connection status (simple connectivity test only) |
| setup_unity_bridgeA | Install/update Unity MCP bridge scripts to a Unity project (works even if Unity server is not running) |
| folder_createC | Create a new folder in Unity project |
| folder_renameC | Rename a folder in Unity project |
| folder_moveC | Move a folder to a new location in Unity project |
| folder_deleteC | Delete a folder from Unity project |
| folder_listB | List contents of a folder in Unity project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are organized by resource type (folder, project, script, shader) and action (create, delete, list, move, rename, read, apply_diff, info, status, setup), making it easy for an agent to select the right tool. There is no overlap in functionality between tools.
Tool names follow a consistent verb_noun pattern throughout, with all names using snake_case. Examples include folder_create, script_read, shader_delete, and project_info. This predictability makes the tool set easy to navigate and understand.
With 15 tools, the count is well-scoped for a Unity MCP server, covering key operations for folders, projects, scripts, and shaders. Each tool earns its place by addressing specific needs in Unity project management, without being excessive or insufficient.
The tool set provides strong coverage for the Unity domain, including CRUD operations for folders, scripts, and shaders, along with project info and setup tools. Minor gaps exist, such as no update tools for scripts or shaders (only create, delete, read, and apply_diff for scripts), but agents can work around these with existing tools like script_apply_diff.