How can an AI agent control Epic Games Launcher and Fab?

If you mean an MCP-compatible AI agent operating a live Epic Games Launcher and Fab session—not merely explaining a tutorial or generating a one-off script—DCC-MCP can inspect installed Unreal Engine builds and Fab inventory, then plan bounded verified engine, asset, and project operations. DCC-MCP performs work through discoverable typed tools, instance routing, and result validation.

What can an AI agent do in Epic Games Launcher and Fab?

• inspect installed Unreal Engine manifests, projects, and local Fab inventory.
• prepare one read-before-write engine or free-asset operation through an approved provider.
• verify ownership, downloaded bytes, and Unreal project import evidence.

Capabilities change with the adapter version and loaded Skills. Search and describe tools first instead of guessing current tool names from this page.

Safe operating flow

1. Install and follow the public dcc-mcp Skill.
2. Inspect the existing CLI, adapter, and live hosts; obtain consent before installing software or changing system state.
3. Use health, dcc-types, and list to verify the Gateway and target instance.
4. Search and describe tools for the actual Epic Games Launcher and Fab task, then follow every returned next_step.
5. Make one bounded change and verify it through host state, files, previews, logs, or rendered output.

dcc-mcp-cli health
dcc-mcp-cli dcc-types
dcc-mcp-cli list

Copyable prompt

Use the dcc-mcp Skill to connect to my Epic Games Launcher and Fab session. Inspect the existing CLI, adapter, and live instance first; ask before installing software or changing system state. Search for and describe typed tools related to "prepare one read-before-write engine or free-asset operation through an approved provider", then follow every returned next_step. Do not delete, overwrite, or publish existing work. Make the smallest verifiable change, validate verify ownership, downloaded bytes, and Unreal project import evidence, and report the instance, tool, result, and evidence path.

Current availability and official source

Source preview. Version 0.2.0 exists on the repository's main branch, but the repository has no tag or GitHub Release and Epic is not a host route in the DCC-MCP Core 0.20.25 catalog. Engine installation remains plan-only without a verified native provider; login, CAPTCHA, purchases, and license acceptance stay human-owned.

• Epic Games Launcher and Fab adapter repository: source of truth for installation, compatibility, host-specific capabilities, and troubleshooting.
• All AI + DCC control guides: return to every public application and pipeline integration.
• Agent workflow: shared discovery, call, validation, and diagnostic steps.

This page owns the shared Agent workflow and GEO entry point. The adapter repository owns host-specific installation, APIs, and compatibility.