Connect Claude Code and Codex to Unreal Engine

NarshaADK is the Fab product. The plugin folder, code module, and runtime executable are named NarshaMCP. You use it with your own MCP client.

Requirements

• Windows 64-bit; an Unreal Engine 5.7 or 5.8 C++ project.
• Visual Studio 2022 with Unreal Engine C++ build tools.
• Claude Code or Codex, tested MCP clients. They are separate products and may require their own subscription.
• No Python or Node.js installation is required for the prebuilt runtime.

Blueprint-only projects are not supported. See compatibility and limitations before installing.

Install

1. Install NarshaADK from the Fab listing and enable the NarshaMCP plugin in a C++ project.
2. Build the project once. The first build runs local setup and writes the project’s MCP configuration, unless installed in plugin-only mode. This build also produces the PDBs used for symbol analysis.
3. Open the local dashboard’s AI Clients section and confirm the Claude Code or Codex connection.

Use the package matching your Unreal Engine version. Before upgrading, back up the project and keep a copy of the previous plugin if you may need to go back. Current download options, pricing, and licenses are on the Fab listing.

Connect your MCP client

The first build normally writes the configuration. For a manual connection, point your client at the runtime inside the plugin. Use forward slashes in the Codex TOML paths.

Replace <Project> with the absolute path to your project. Code and tool names are the same in both languages.

MCP configuration

{
  "mcpServers": {
    "narshamcp": {
      "command": "<Project>/Plugins/NarshaMCP/Source/ThirdParty/bin/narshamcp.exe",
      "args": ["connect", "--project-path", "<Project>"],
      "env": { "RUST_LOG": "error" }
    }
  }
}

Claude Code

claude mcp add narshamcp -- "<Project>/Plugins/NarshaMCP/Source/ThirdParty/bin/narshamcp.exe" connect --project-path "<Project>"

Codex — ~/.codex/config.toml

[mcp_servers.narshamcp]
command = "<Project>/Plugins/NarshaMCP/Source/ThirdParty/bin/narshamcp.exe"
args = ["connect", "--project-path", "<Project>"]

connect attaches to the project’s background daemon and starts it when none is running. Clients that launch a direct server process, such as Cursor, use --stdio in place of connect.

Verify the connection

Ask your client to call ue_check_health. The response includes status and version. On first start, the server indexes the PDBs from your build.

Response	What to do
symbol_index_loading	Indexing is in progress. A progress object appears once the total is known. Try the symbol operation again when indexing finishes.
symbol_index_degraded_budget	A memory budget capped the index. Waiting does not clear this state; inspect health and index configuration before relying on complete symbol results.

Tool parameters can change during Early Access. Ask ue_tool_docs for current operations and parameters; your client lists tools through tools/list.

Try a first read

Ask: “Which Blueprints call this C++ function?” Use a function in your own project. The recorded Lyra examples show real requests, responses, and their limitations.

Most reads work with the Editor closed; asset-changing operations need a running Editor. For help, use the support channel on the Fab listing.