VibeUE

MCP Server for Unreal Engine

AI CLIENT SETUP

Connect your AI coding assistant to VibeUE's MCP server

VibeUE runs a built-in HTTP MCP server at http://127.0.0.1:8088/mcp when Unreal Editor is open. Connect your AI client to this server to give it full control over Unreal Engine.

Each AI tool also benefits from project instructions — a copy of VibeUE's API rules and skills guide that tells the AI how to use the MCP tools correctly. Without these, the AI will guess and fail.

📁 FAB users — finding your instructions file: FAB installs to a non-obvious path. Open the VibeUE Settings (⚙️ gear icon in the chat window) — the full plugin path is shown under the MCP Server section with an Open Folder button. Your sample instructions file is at Content/samples/instructions.sample.md inside that folder.

Two things to set up:

1. MCP connection — connects the AI to Unreal

2. Project instructions — teaches the AI how to use VibeUE

MCP server must be running:

Enable via Project Settings > Plugins > VibeUE. Server only runs when Unreal Editor is open.

Optional: Keep Tools Available Before UE Launches

By default, the MCP server only runs while Unreal Editor is open — so your AI client shows a connection error until you launch UE first. The VibeUE MCP Proxy runs in the background and keeps your tool list visible at all times, even before UE starts. You can also have Claude start it automatically at the beginning of each session.

Set up the MCP Proxy

Claude Code ✅ Recommended

1. Connect MCP Server

Run once in your terminal to register VibeUE globally:

claude mcp add --scope user --transport stdio VibeUE-Claude -- npx -y mcp-remote http://127.0.0.1:8088/mcp --transport http-only --allow-http --header "Authorization:Bearer YOUR_API_KEY"

Omit the --header argument if no API key is set in VibeUE. Use --scope project to limit to a single project.

2. Add Project Instructions (import supported)

Create CLAUDE.md at your Unreal project root. The @ directive inlines the file automatically — no copying needed.

# My Unreal Project

<!-- Add project-specific notes here -->

@Plugins/VibeUE/Content/samples/instructions.sample.md

The sample includes all 22 VibeUE skills, MCP tool guidance, and log reading instructions. It stays up to date as VibeUE is updated.

GitHub Copilot

1. Connect MCP Server

Create .vscode/mcp.json in your Unreal project root:

{
  "servers": {
    "VibeUE": {
      "type": "http",
      "url": "http://127.0.0.1:8088/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Omit the headers section if no API key is set in VibeUE.

2. Add Project Instructions (copy required)

Copilot does not support file imports. Copy the instructions file to:

.github/copilot-instructions.md
cp Plugins/VibeUE/Content/samples/instructions.sample.md .github/copilot-instructions.md

Re-copy after VibeUE updates to keep instructions in sync.

Cursor

1. Connect MCP Server

Create or edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):

{
  "mcpServers": {
    "VibeUE": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://127.0.0.1:8088/mcp",
        "--transport",
        "http-only",
        "--allow-http",
        "--header",
        "Authorization:Bearer YOUR_API_KEY"
      ]
    }
  }
}

Omit the last two --header args if no API key is set in VibeUE.

2. Add Project Instructions (copy required)

Cursor does not support file imports. Copy the instructions file to:

.cursor/rules/vibeue.mdc
cp Plugins/VibeUE/Content/samples/instructions.sample.md .cursor/rules/vibeue.mdc

Re-copy after VibeUE updates to keep instructions in sync.

Google Antigravity

1. Connect MCP Server

Create .agent/mcp.json in your Unreal project root:

{
  "mcpServers": {
    "VibeUE": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://127.0.0.1:8088/mcp",
        "--transport",
        "http-only",
        "--allow-http",
        "--header",
        "Authorization:Bearer YOUR_API_KEY"
      ]
    }
  }
}

Omit the last two --header args if no API key is set in VibeUE.

2. Add Project Instructions (copy required)

Antigravity does not support file imports. Copy the instructions file to your workspace rules directory:

.agent/rules/vibeue.md
cp Plugins/VibeUE/Content/samples/instructions.sample.md .agent/rules/vibeue.md

Re-copy after VibeUE updates to keep instructions in sync.

Claude Desktop

Connect MCP Server

Edit your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "VibeUE": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://127.0.0.1:8088/mcp",
        "--transport",
        "http-only",
        "--allow-http",
        "--header",
        "Authorization:Bearer YOUR_API_KEY"
      ]
    }
  }
}

Restart Claude Desktop after saving. Omit the --header args if no API key is set in VibeUE.

Note: Claude Desktop does not support project-level instruction files. Use Claude Code for the best VibeUE experience.
Tip: Since Claude Desktop launches independently of Unreal Engine, you may hit a connection error if UE isn't already open. The VibeUE MCP Proxy keeps tools available at all times so Claude Desktop connects cleanly on startup.

VS Code

Connect MCP Server

Create .vscode/mcp.json in your Unreal project root:

{
  "servers": {
    "VibeUE": {
      "type": "http",
      "url": "http://127.0.0.1:8088/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Omit the headers section if no API key is set in VibeUE. VS Code supports native HTTP MCP — no mcp-remote bridge needed.

Tip: If using VS Code with GitHub Copilot, see the GitHub Copilot section above for project instructions setup.