Copy asset packages and their dependencies into project content through Unreal Editor's native MCP server.

What it does

• Preview dependency copies before writing with a dry run.

• Keep folder structure, reuse existing destination packages and report conflicts.

• Optionally repoint project referencers to copied assets.

• Refresh material function calls after copying.

Requirements

Unreal Engine 5.8, Windows 64-bit editor. Enable ToolsetRegistry, ModelContextProtocol. Connect an HTTP MCP-compatible client to the native editor server. Editor only; source and documentation included. No project or third-party asset packs are included.

Documentation and support

https://github.com/ITemre/AssetCopyAIToolset

https://github.com/ITemre/AssetCopyAIToolset/issues

Limitations

• Copying assets does not grant redistribution rights. Check the source asset licence before shipping or reselling any copied content.

• Copy and reference-repointing operations save files and are not guaranteed to be reversible with Ctrl+Z. Keep a project backup.

• Header-patching mode is an advanced workflow. Review conflicts, external references and stray-copy reports before a real run.

Validation

Built and checked in UE 5.8.4 on Windows. 15 internal automation tests passed, plus real plugin-content copy, dependency reuse and header-patching checks. Expected rejection diagnostics are included where applicable. See the public validation notes for fixture scope and limitations.

Actual copying uses plugin content roots; base /Engine assets are not supported by Unreal Advanced Copy.