Terminal
Terminal/Skill
Guide for using the Unity Asset Manager MCP to create, version, upload, and organize assets in Unity Cloud.
By Unity
Works with
npx skills add unity-technologies/industry-ai-workflows --skill asset-manager-authoringGuide for driving the Asset Manager MCP (Asset_Manager_MCP) to publish and
organize assets in Unity Cloud. This is the endpoint both Asset Transformer skills
point at when they say "chain an Asset Manager action" / "push the result to
Asset Manager": once an AT workflow has produced a local file (GLB, FBX, etc.),
the tools here create the asset and upload it.
Almost every tool takes asset_name as the primary handle, plus an
org/project scope. You rarely pass raw asset IDs:
org_id / project_id
args → project_name (resolved by name) → the session defaults set via
set_default_organization / set_default_project.list_organizations → ask the user →
set_default_organization, then list_projects → set_default_project (or
set_default_project_by_name; offer create_project when none fits), then
omit the scope on later calls.list_organizations, list_projects, list_assets.The MCP authenticates the same way as Pipeline Automation:
unity_login (browser PKCE) once; tokens are cached and refreshed automatically.unity_auth_status. If a call fails with an auth error, that's
the first thing to verify — don't retry blindly.The canonical publish flow:
create_asset — creates the asset, or a new uploadable version if it
already exists. Returns the asset/version to upload into. tags must be a
list (["a", "b"]). asset_type takes the dashboard's spaced values
("3D Model", "Prefab", "Scene", "Shader", ...; legacy unspaced spellings are
mapped) — pick the specific type, and use change_asset_type to retype an
existing asset. New assets default to "3D Model"; on a re-version, leaving
it empty keeps the current type.upload_files_to_asset — uploads local files to the current (unfrozen)
version. model_files is a list of local paths. freeze_after_upload=True
freezes in one step.upload_preview_image_to_asset (optional) — uploads a thumbnail to the
preview dataset. The asset must already exist with an unfrozen version.freeze_asset — freezes the current version. Freezing is required before
a new version can be created.change_asset_status — advance the asset's status (e.g. to Published). If
the requested status isn't directly reachable, the tool reports the reachable
ones rather than forcing it. get_asset_status reads the current status and
reachable transitions without changing anything.Then get_asset_url returns the dashboard link — surface it to the user.
To revise an existing asset: create_new_draft_version (or create_asset again
with the same name) → upload_files_to_asset → freeze_asset. You must freeze the
previous version before a new draft can be created.
batch_upload_assets — create + upload many assets in one call.download_files_from_asset — pull an asset's files locally (e.g. to feed
into an Asset Transformer run_python import).update_asset_metadata — merges custom metadata fields into an asset
(fields not supplied are left untouched).list_field_definitions, create_field_definition, delete_field_definition.
Setting metadata for an undefined field will not stick — define it first.list_asset_labels shows the labels on an asset's versions
("Latest"/"Pending" are system-assigned). User labels are fully manageable:
create_label defines one at the org level, assign_label/unassign_label
attach it to an asset's current version, list_labels shows the org's labels.search_assets_across_projects searches the whole org
when you don't know which project holds an asset; list_asset_versions shows
an asset's full version history including old frozen versions.delete_asset with
delete_all_versions=True soft-deletes to the trash; list_trashed_assets +
restore_asset bring things back. Pass trash=False only for a deliberate
permanent removal.Recently extended with relativePath and reference metadata — use them:
add_asset_reference — link source_asset_name → target_asset_name
within a project. Options:
dependency_type — the kind of dependency.target_label — resolve the target by label.relative_path — the path the source expects the target at (e.g. a texture's
location relative to a model). Set this when the consumer needs the dependency
laid out at a specific path.metadata — arbitrary metadata on the reference itself.list_asset_references — context = source | target | both (unrecognized values fall back to both).remove_asset_reference — drop a link.Organize assets into collection paths:
list_collections, create_collection, delete_collection,
link_asset_to_collection, unlink_asset_from_collection. upload_files_to_asset
and batch_upload_assets also accept a collection_path to place the asset on
upload.
list_organizations, list_projects, create_project, delete_project,
set_default_project, set_default_project_by_name.
at-scripting / run_python): the AT MCP writes a file to a
local path; then call create_asset + upload_files_to_asset (this skill) to
publish it. There is no direct "AT writes to AM" call — it's two steps.at-upa-scripting): the custom-script action has no AM
credentials, so you chain the pipeline's Create asset / Add file actions
instead (see pipeline-authoring). That's a different mechanism from this MCP.tags and other list-typed params must be arrays, not comma-strings.*_name) and a session default project over threading
IDs through every call — but pass explicit IDs when acting across projects.get_asset_url so the user can verify in the portal.Create asset / Add file actions and their parameters → see
pipeline-authoring (known-action-ids.md). Those run inside a pipeline, not
via this MCP.at-scripting (in-process) and
at-upa-scripting (pipeline custom scripts).