Delete one or more Unity C# script files and their accompanying .meta files when present. Refresh the asset database, then wait for Unity to finish recompiling before delivering the final result.
Delete one or more `.cs` script files from disk, refresh the AssetDatabase, and wait for Unity compilation to settle before delivering the final result via the request's `requestId`. Pair with 'script-read' to inspect files before deletion.
Review the instructions the agent will receive before you install.
Delete the script file(s). Does AssetDatabase.Refresh() and waits for Unity compilation to complete before reporting results. Use 'script-read' tool to read existing script files first.
files — non-empty array of .cs paths. Every entry must exist on disk.requestId — required for the processing/delivered-later contract.Validates the array (non-empty, every entry ends with .cs, every entry exists). Deletes each file plus its sibling .meta (when present). Calls AssetDatabase.Refresh and schedules a post-compilation notification — the final response is delivered after Unity finishes the recompile triggered by the delete.
unity-mcp-cli run-tool script-delete --input '{
"files": "string_value"
}'
For complex input (multi-line strings, code), save the JSON to a file and use:
unity-mcp-cli run-tool script-delete --input-file args.jsonOr pipe via stdin (recommended):
unity-mcp-cli run-tool script-delete --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 |
|---|---|---|---|
files | any | Yes | File paths to the files. Sample: "Assets/Scripts/MyScript.cs". |
{
"type": "object",
"properties": {
"files": {
"$ref": "#/$defs/System.String-1"
}
},
"$defs": {
"System.String-1": {
"type": "array",
"items": {
"type": "string"
}
}
},
"required": [
"files"
]
}
This tool does not return structured output.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Build unity-mcp-cli from its TypeScript source and optionally make the command available across terminals with npm link. Covers dependency installation, compilation, version checks, and reporting errors when a step fails.
Save changed scenes and assets, then quit a Unity Editor started by a CLI session. A matching session identifier is required, and editors opened manually are left running. Headless editors are supported.
Review unresolved GitHub pull request comments against the current code, apply minimal fixes for valid issues, and reply to review threads. Comments that need human judgment remain open, while fixed or unnecessary requests are resolved with explanations.
Add packages to a Unity project from its package registry, a Git URL, or a local path. Choose a compatible version or specify one, and receive the installation result after any required reload.
List packages installed in a Unity project with their names, versions, sources, and descriptions. Filter by source or keyword, or show only direct dependencies—the packages explicitly listed in the project manifest.
Remove an installed UPM package, a package managed by Unity, from a project. Checks that it exists, updates manifest.json, and delivers the result after any reload. Built-in packages and dependencies of other packages cannot be removed.