build-cli
Build the unity-mcp-cli TypeScript CLI tool and link it globally for terminal use.
Add one or more Components to a GameObject in the opened Prefab or active Scene. Component types are looked up by full name (with namespace) or by class-name fallback. Use 'gameobject-find' to locate the host GameObject and 'gameobject-component-list-all' to discover valid
$ npx -y skills add IvanMurzak/Unity-MCP --skill gameobject-component-add --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/gameobject-component-addContext preview
The summary Claude sees to decide when to auto-load this skill.
Add one or more Components to a GameObject in the opened Prefab or active Scene. Component types are looked up by full name (with namespace) or by class-name fallback. Use 'gameobject-find' to locate the host GameObject and 'gameobject-component-list-all' to discover valid
name: gameobject-component-add description: Add one or more Components to a GameObject in the opened Prefab or active Scene. Component types are looked up by full name (with namespace) or by class-name fallback. Use 'gameobject-find' to locate the host GameObject and 'gameobject-component-list-all' to discover valid component type names.
Add Component to GameObject in opened Prefab or in a Scene. Use 'gameobject-find' tool to find the target GameObject first. Use 'gameobject-component-list-all' tool to find the component type names to add.
Per-name errors (unknown type, type not assignable to `UnityEngine.Component`, add-failed/duplicate) are accumulated in `response.Errors` / `response.Warnings` instead of throwing, so a single bad name does not abort the whole batch. Successful additions populate `response.AddedComponents` with `ComponentDataShallow` snapshots.
unity-mcp-cli run-tool gameobject-component-add --input '{
"componentNames": "string_value",
"gameObjectRef": "string_value"
}'> For complex input (multi-line strings, code), save the JSON to a file and use: > ```bash > unity-mcp-cli run-tool gameobject-component-add --input-file args.json > ``` > > Or pipe via stdin (recommended): > ```bash > unity-mcp-cli run-tool gameobject-component-add --input-file - <<'EOF' > {"param": "value"} > EOF > ```
If `unity-mcp-cli` is not found, either install it globally (`npm install -g unity-mcp-cli`) or use `npx unity-mcp-cli` instead. Read the /unity-initial-setup skill for detailed installation instructions.
| Name | Type | Required | Description | |------|------|----------|-------------| | `componentNames` | `any` | Yes | Full name of the Component. It should include full namespace path and the class name. | | `gameObjectRef` | `any` | Yes | Find GameObject in opened Prefab or in the active Scene. |
{
"type": "object",
"properties": {
"componentNames": {
"$ref": "#/$defs/System.String-1"
},
"gameObjectRef": {
"$ref": "#/$defs/AIGD.GameObjectRef"
}
},
"$defs": {
"System.String-1": {
"type": "array",
"items": {
"type": "string"
}
},
"System.Type": {
"type": "string"
},
"AIGD.GameObjectRef": {
"type": "object",
"properties": {
"instanceID": {
"type": "integer",
"description": "instanceID of the UnityEngine.Object. If it is '0' and 'path', 'name', 'assetPath' and 'assetGuid' is not provided, empty or null, then it will be used as 'null'. Priority: 1 (Recommended)"
},
"path": {
"type": "string",
"description": "Path of a GameObject in the hierarchy Sample 'character/hand/finger/particle'. Priority: 2."
},
"name": {
"type": "string",
"description": "Name of a GameObject in hierarchy. Priority: 3."
},
"assetType": {
"$ref": "#/$defs/System.Type",
"description": "Type of the asset."
},
"assetPath": {
"type": "string",
"description": "Path to the asset within the project. Starts with 'Assets/'"
},
"assetGuid": {
"type": "string",
"description": "Unique identifier for the asset."
}
},
"required": [
"instanceID"
],
"description": "Find GameObject in opened Prefab or in the active Scene."
}
},
"required": [
"componentNames",
"gameObjectRef"
]
}{
"type": "object",
"properties": {
"result": {
"$ref": "#/$defs/AIGD.AddComponentResponse"
}
},
"$defs": {
"System.Collections.Generic.List(AIGD.ComponentDataShallow)": {
"type": "array",
"items": {
"$ref": "#/$defs/AIGD.ComponentDataShallow"
}
},
"AIGD.ComponentDataShallow": {
"type": "object",
"properties": {
"instanceID": {
"type": "integer"
},
"typeName": {
"type": "string"
},
"isEnabled": {
"type": "string",
"enum": [
"False",
"True",
"NA"
]
}
},
"required": [
"instanceID",
"isEnabled"
]
},
"System.Collections.Generic.List(System.String)": {
"type": "array",
"items": {
"type": "string"
}
},
"AIGD.AddComponentResponse": {
"type": "object",
"properties": {
"AddedComponents": {
"$ref": "#/$defs/System.Collections.Generic.List(AIGD.ComponentDataShallow)",
"description": "List of successfully added components."
},
"Messages": {
"$ref": "#/$defs/System.Collections.Generic.List(System.String)",
"description": "List of success messages for added components."
},
"Warnings": {
"$ref": "#/$defs/System.Collections.Generic.List(System.String)",
"description": "List of warnings encountered during component addition."
},
"Errors": {
"$ref": "#/$defs/System.Collections.Generic.List(System.String)",
"description": "List of errors encountered during component addition."
}
}
}
},
"required": [
"result"
]
}Get up and running in three steps: Install plugin — download the .unitypackage installer or run openupm add com.ivanmurzak.unity.mcp Alternative: npx unity-mcp-cli install-plugin ./MyUnityProject — see CLI documentation Pick an AI agent — Claude Code, Claude
Repo: IvanMurzak/Unity-MCP
Build the unity-mcp-cli TypeScript CLI tool and link it globally for terminal use.
Review and resolve PR comments from GitHub. Validates each comment, fixes legitimate issues.
Copy assets at given paths and store them at new paths. Refreshes the AssetDatabase at the end. Use 'assets-find' to locate the source assets first.
Create a new folder under a parent folder inside 'Assets/'. The parent path must start with 'Assets/' and every intermediate folder in it must already exist.…
Delete the assets at the given project paths. Refreshes the AssetDatabase at the end. Use 'assets-find' to locate the assets first.
Search the built-in assets of the Unity Editor (located at Resources/unity_builtin_extra). Filters by name and/or type; built-in assets have no GUID so…