# vedantrgosavi/ue5-mcp architecture

> Architecture diagram of the GitHub repository vedantrgosavi/ue5-mcp, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-04-01). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/vedantrgosavi/ue5-mcp
- Repository: https://github.com/vedantrgosavi/ue5-mcp

## Overview

##### Main Components
- AI Integration Module – This component drives the automation features (as referenced by ai_integration.md) and coordinates commands/automation in both Blender and UE5.
- Blender Automation & Scene Generation – Represent this as the Blender side of the pipeline. It includes modules for text-to-scene conversion, image-based creation, asset generation, material/texture management, and the integration of assets from sources like PolyHaven. Note that it builds upon functionality described in BlenderMCP (see blender_mcp.md).
- UE5 Integration & Level Conversion – This module handles importing externally generated scenes from Blender, converting them into UE5 game levels, managing materials, lighting, level optimization, and even Blueprint-based scene manipulation.
- Asset Management and Gameplay Programming – Although closely tied with Blender and UE5 modules, it can be shown as a support component that ensures assets (3D models, textures) are correctly generated and transferred. It also includes debugging and performance profiling for the final game level.
- Configuration & Dependency Management – Even though this doesn’t enact runtime logic, show a supporting block that represents configurations (configurations.md), dependencies details (dependencies.md), and commands (commands.md) which influence how the system is run.
- Workflow Orchestrator – Given the multiple steps in the pipeline (from asset generation in Blender to level integration in UE5), include a component that orchestrates the entire workflow (guided by workflow.md & automation.md).

##### Relationships and Interactions
- Feedback loops where performance profiling and automated debugging (in UE5) feed back into further refinements in scene generation or asset management.

##### Architectural Patterns and Design Principles
- Clearly separate components based on responsibility: data processing (AI integration), scene generation (Blender), and game level production (UE5).
- How the design leverages an “orchestration” or “pipeline” pattern—each stage in the pipeline feeds forward to the next.

##### Relevant Technologies and Frameworks
- For Blender: Python scripting and Blender’s internal automation systems.
- For UE5: Blueprint scripting and possibly Unreal Engine’s automation or plugin systems.
- Underline that Python 3.x is the language used to tie these tools together (as noted in README prerequisites).
- Mention any AI-driven libraries or tools specified in ai_integration.md that are key for automation.

##### Elements

- Branch into two parallel pipelines:
- Left Pipeline: Blender Side that includes AI-driven scene generation, asset creation, and material management.
- Right Pipeline: UE5 Side for automated scene import, level conversion, blueprint manipulation, and debugging.
- Annotations or brief notes specifying the role of each component and reference corresponding documentation files for further depth.

## Diagram (Mermaid)

```mermaid
flowchart TB
    subgraph "Workflow Orchestration Layer"
        F["Workflow Orchestrator"]:::orchestration
        A["AI Integration Engine"]:::ai
        F -->|"orchestrates"| A
    end

    subgraph "Processing Pipeline"
        subgraph "Blender Side"
            B["Blender Automation & Scene Generation"]:::blender
        end
        subgraph "UE5 Side"
            C["UE5 Integration & Level Conversion"]:::ue5
        end
        D["Asset Management & Gameplay Programming"]:::asset
        A -->|"commands"| B
        A -->|"commands"| C
        B -->|"scene_transfer"| C
        B -->|"assets"| D
        D -->|"asset_flow"| C
        C -->|"feedback"| B
    end

    E["Configuration & Dependency Management"]:::config
    E -->|"influences"| B
    E -->|"influences"| C
    F -->|"orchestrates_assets"| D

    %% Click Events
    click F "https://github.com/vedantrgosavi/ue5-mcp/blob/main/workflow.md"
    click A "https://github.com/vedantrgosavi/ue5-mcp/blob/main/ai_integration.md"
    click B "https://github.com/vedantrgosavi/ue5-mcp/blob/main/blender_mcp.md"
    click C "https://github.com/vedantrgosavi/ue5-mcp/blob/main/ue5_mcp.md"
    click E "https://github.com/vedantrgosavi/ue5-mcp/blob/main/configurations.md"

    %% Styles
    classDef orchestration fill:#fed9a6,stroke:#000,stroke-width:2px;
    classDef ai fill:#b3cde0,stroke:#000,stroke-width:2px;
    classDef blender fill:#ccebc5,stroke:#000,stroke-width:2px;
    classDef ue5 fill:#decbe4,stroke:#000,stroke-width:2px;
    classDef asset fill:#fbb4ae,stroke:#000,stroke-width:2px;
    classDef config fill:#ffffcc,stroke:#000,stroke-width:2px;
```
