IDE/Claude Code (Alpha)

Overview

Supercharge your favorite IDE or AI coding assistant with Aura's Unreal and Unity intelligence.

The one-click integration with Claude Code, Visual Studio, Cursor, and Rider (Junie) makes it easy to get started.

Aura exposes its tools via MCP (Model Context Protocol), letting you drive Unreal or Unity from any MCP-compatible environment — generate blueprints, analyze UAssets, edit scenes and prefabs, run C# editor scripts, and generate images and 3D assets.

This lets you:

• Use your existing AI subscriptions (Claude, Copilot, etc.) with Aura's tools
• Work in your preferred IDE while controlling Unreal or Unity
• Save 50-75% on non-essential tasks by using your own AI subscription

Watch the walkthrough on setting up Aura with Claude Code in this video at the 1:11 timestamp.

Requirements

• Aura for Unreal or Aura for Unity must be running. Unreal can be launched automatically via the launch_unreal_project tool if not already open
• Requires a paid Aura subscription or active trial

Billing

Subagents like Python Agent and Blueprint Agent use Aura's specialized intelligence and are charged to your Aura subscription, not your IDE's AI subscription. Your API costs for other platforms may increase significantly while using Aura's intelligence.

Limitations

• Less seamless than using Aura directly in Unreal or Unity — you need to know which tools to invoke
• Existing MCP Configurations including Auto-generated comments in some IDE MCP configs can break the one-click install
• MCP server removal must be done manually in your IDE's config
• Integrations are only set up with one project at a time — to switch, remove the existing server block and re-add it from the new project.

Unreal Setup

One-Click Setup

1. Open Aura in Unreal
2. Click the Settings icon
3. Click MCP Configuration
4. Click Add to Editor
5. Select your IDE (Claude Code, Visual Studio, Cursor, or Rider)
6. Restart your IDE completely before using

⚠️ If you have existing MCP configurations or non-default settings, the one-click install may not work. Follow the manual setup below instead.

Manual Setup

If one-click doesn't work, copy the MCP config manually. Aura for Unreal installs two servers — unreal_inspector (read-only inspection and planning) and unreal_editor (authoring and mutation). All MCP-compatible IDEs use the same basic structure:

{
  "servers": {
    "unreal_inspector": {
      "type": "stdio",
      "command": "path/to/python.exe",
      "args": ["path/to/Aura/MCP/unreal_inspector.py"]
    },
    "unreal_editor": {
      "type": "stdio",
      "command": "path/to/python.exe",
      "args": ["path/to/Aura/MCP/unreal_editor.py"]
    }
  }
}

The exact command and args values for both servers come from Aura's Settings → MCP Configuration page.

Unity Setup

Quick Setup

1. Open AuraForUnity and connect it to your Unity project
2. Click the Settings icon
3. Click MCP Configuration
4. Copy the displayed aura-unity server block into your IDE's MCP config (see locations below)
5. Restart your IDE completely before using

Manual Setup

Add the following server block to your IDE's MCP config:

{
  "servers": {
    "aura-unity": {
      "type": "stdio",
      "command": "path/to/AuraForUnity/python/python.exe",
      "args": ["-m", "aura_unity_mcp.server"]
    }
  }
}

The exact command path is shown on AuraForUnity's Settings → MCP Configuration page. On Windows the Python executable typically lives at %LOCALAPPDATA%\Programs\AuraForUnity\python\python.exe.

ℹ️ Aura for Unity must be running and connected to your Unity project for the MCP tools to respond. If the connection drops, the IDE will see tool errors until you reopen the project in AuraForUnity.

Config file locations

The Unreal (unreal_inspector, unreal_editor) and Unity (aura-unity) server blocks all go into the same per-IDE MCP config file:

• Claude Code — ~/.claude/mcp.json
• Cursor — .cursor/mcp.json in workspace, or global settings
• Visual Studio — ~/.mcp.json (global user config)
• Rider / JetBrains — Settings → Tools → AI Assistant → MCP Servers
• VS Code — .vscode/mcp.json (manual setup only; not a one-click target)

After adding the config, restart your IDE completely and verify Aura tools appear in your AI assistant's tool picker.

Available Tools

For Unreal

Aura for Unreal exposes its capabilities through two MCP servers, installed and configured together by the one-click setup:

unreal_inspector

Inspects project state without changing it: asset metadata and graphs, blueprint review, asset and code search, logs, read-only Python queries, and engine lifecycle (launch/recompile/shutdown), plus planning, skill references, and image/3D-model generation.

unreal_editor

Makes changes in the editor: Blueprint and C++ authoring, materials, Niagara VFX, behavior trees, data tables, UMG widgets, Enhanced Input, and Unreal Python — plus Play-In-Editor control and verification (input simulation, screenshots, profiling).

For Unity

aura-unity

Exposes the full Unity editor surface — scene and GameObject CRUD, components, prefabs and variants, materials, terrain, animation, Input System, UI, packages, profiler, and execute_script for arbitrary C# editor scripts — plus server-side image, 3D-model, and screenshot generation. See the Unity Scene & Prefab, Unity Coding (C#), and Unity Editor Agent pages for the full list.

Troubleshooting

Tools not appearing: Restart your IDE completely after adding the MCP config.

Connection errors: Ensure Aura (Unreal) has a green connection indicator, or that AuraForUnity shows your Unity project as connected.

Config conflicts: If you have other MCP servers configured, add Aura manually to avoid conflicts.