楽AI — The Universal Runtime for World Models  |  For Studios & Developers →    Also: Read the MCP build log →

Documentation

Supercharge your AI in the real world.

Drive the RakuAI runtime from any AI assistant over the 17-tool native MCP surface. 18ms motion-to-photon. Sub-millimeter spatial precision. Built for glasses, not laptops.

Documentation map: an AI assistant reaches the RakuAI runtime over the 17-tool native MCP surface, and the runtime drives the spatial engine, XR features and AI systems subsystems. AI assistant Claude · ChatGPT · Gemini · Copilot 17-tool native MCP permission-gated RakuAI Runtime deterministic authority Spatial Engine physics · audio · effects XR Features input · tracking · anchoring AI Systems NPCs · voice · adaptive play
How the docs fit together: one MCP surface in front of the runtime and its subsystems.

Why RakuAI?

Five granted US patents. Priority July 2012. Decade-old IP that anchors today’s AR-glasses category. The runtime that Claude, ChatGPT, Gemini, and Copilot all drive — multi-vendor by design.

Built for glasses, not laptops

18ms motion-to-photon latency. Sub-millimeter spatial precision. OpenXR conformant on Meta Quest 3, Xreal Air, Samsung Android XR, and MiRZA AR2.

World-model orchestration

17-tool native MCP surface for world-model orchestration. Every frame, every NPC, every interaction routed through the AI of your choice. Unity’s MCP targets scene manipulation at design time — RakuAI’s MCP runs at runtime, every frame.

Industrial-grade surface

18 native DLLs. 17 router modules. 9,500+ REST endpoints. 10,328 bound engine functions. The boring numbers behind a fun-feeling runtime.

Getting Started

1

Connect Your AI Assistant

Wire the RakuAI MCP server into Claude Desktop (or any MCP-capable client). The 17 native tools appear natively in your conversations. Claude Desktop guide →

2

Drive the Runtime

Call get_metrics or get_scene_state for read-only inspection in any environment. In sandbox/dev, load adapters, ingest frames, configure render targets, and start simulations. The engine remains the authority on physics, collision, and scoring.

3

Read the Build Log

The full reasoning behind the 17-tool native surface — why these tools, what the adapters unlock next — is in the blog. Read the MCP build log →

Engine Feature Guides

Deep dives into the core engine subsystems. Each guide covers architecture, API examples, and performance characteristics.

Spatial Engine

Physics, animation, visual effects, and immersive spatial audio for 3D worlds.

Explore Spatial Engine →

XR Features

Complete XR development platform with natural input, immersive feedback, mixed reality, and cross-headset compatibility.

Explore XR Features →

AI Systems

Intelligent NPC systems, voice interaction, and adaptive gameplay.

Explore AI Systems →

The 17 Native MCP Tools

Every external agent reaches the engine through the same 17 native tools — get_scene_state, add_scene_node, load_world_model, … (5 read-only + 12 mutation; see mcp.html). Standard contract, any agent.

Supported AI Clients

Wire Up Claude Desktop → for the auto-config script and the full tool reference

Claude Desktop

Native MCP support. PowerShell auto-config script in the developer portal; manual JSON instructions for any platform.

Cursor & IDE Clients

Any MCP-capable editor or IDE can reach the runtime over the same 17-tool native surface. Wiring guides shipping next.

Custom Agents

Build your own agent on the MCP boundary. Read-only tools work in production; mutating tools are sandbox/dev only, deny-by-default.

Bring Your Own LLM

The MCP surface is model-agnostic. ChatGPT custom GPTs, Gemini, Llama, and in-house models all speak the same contract.

Architecture Overview

The engine is the deterministic authority. World models — video predictors, neural radiance fields, physics foundation models — are contributors that plug in over MCP adapters. None of them override the engine’s authority on what is actually happening in the simulation.

Full adapter schemas and integration kits are available with SDK access. Request access →

See the adapter contract on GitHub →

API Reference

REST endpoints for the developer console, MCP server reference, and adapter manifest documentation. The full developer kit is available under NDA.

Developer API Docs

Pro Features

Advanced systems available with RakuAI Pro including standalone export, multiplayer, cloud services, and professional tooling.

See All Pro Features →