build-cli
Build the unity-mcp-cli TypeScript CLI tool and link it globally for terminal use.
List the fully-qualified C# type names of every concrete `UnityEngine.Component` subclass available in the project. Paginated (default 5/page, max 500). Use this to find a valid `componentName` for 'gameobject-component-add'.
$ npx -y skills add IvanMurzak/Unity-MCP --skill gameobject-component-list-all --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/gameobject-component-list-allContext preview
The summary Claude sees to decide when to auto-load this skill.
List the fully-qualified C# type names of every concrete `UnityEngine.Component` subclass available in the project. Paginated (default 5/page, max 500). Use this to find a valid `componentName` for 'gameobject-component-add'.
name: gameobject-component-list-all description: List the fully-qualified C# type names of every concrete `UnityEngine.Component` subclass available in the project. Paginated (default 5/page, max 500). Use this to find a valid `componentName` for 'gameobject-component-add'.
List C# class names extended from UnityEngine.Component. Use this to find component type names for 'gameobject-component-add' tool. Results are paginated to avoid overwhelming responses.
Enumerates `AllComponentTypes` (every non-abstract subclass of `UnityEngine.Component`), filters by `search` if supplied, then returns a `ComponentListResult` containing the requested page plus `TotalCount` / `TotalPages` so the caller can iterate.
unity-mcp-cli run-tool gameobject-component-list-all --input '{
"search": "string_value",
"page": 0,
"pageSize": 0
}'> For complex input (multi-line strings, code), save the JSON to a file and use: > ```bash > unity-mcp-cli run-tool gameobject-component-list-all --input-file args.json > ``` > > Or pipe via stdin (recommended): > ```bash > unity-mcp-cli run-tool gameobject-component-list-all --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 | |------|------|----------|-------------| | `search` | `string` | No | Substring for searching components. Could be empty. | | `page` | `integer` | No | Page number (0-based). Default is 0. | | `pageSize` | `integer` | No | Number of items per page. Default is 5. Max is 500. |
{
"type": "object",
"properties": {
"search": {
"type": "string"
},
"page": {
"type": "integer"
},
"pageSize": {
"type": "integer"
}
}
}{
"type": "object",
"properties": {
"result": {
"$ref": "#/$defs/AIGD.ComponentListResult"
}
},
"$defs": {
"System.String-1": {
"type": "array",
"items": {
"type": "string"
}
},
"AIGD.ComponentListResult": {
"type": "object",
"properties": {
"Items": {
"$ref": "#/$defs/System.String-1",
"description": "Array of component type names for the current page."
},
"Page": {
"type": "integer",
"description": "Current page number (0-based)."
},
"PageSize": {
"type": "integer",
"description": "Number of items per page."
},
"TotalCount": {
"type": "integer",
"description": "Total number of matching components."
},
"TotalPages": {
"type": "integer",
"description": "Total number of pages available."
}
},
"required": [
"Page",
"PageSize",
"TotalCount",
"TotalPages"
]
}
},
"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…