Supercharge your AI in the real world.
The standard contract any AI assistant uses to drive the RakuAI runtime — 17 native MCP tools, adapter manifests, scene-state snapshots. 9,500+ REST endpoints. 10,328 bound engine functions.
The MCP server exposes a fixed surface — get_scene_state, add_scene_node, load_world_model, … (5 read-only + 12 mutation; see mcp.html). Read-only tools work in every mode; mutating tools are sandbox/dev only.
Drive the runtime from Claude Desktop, Cursor, custom GPTs, or any MCP-capable client. The tool surface is the same. Wiring guides for Claude Desktop are live now; more clients are in flight.
Wire up Claude Desktop →Full server, adapter, and scene-state schemas are available under NDA. Request NDA access for the complete integration kit.
Every external agent reaches the engine through the same 17 native tools. Deny-by-default permissions, typed schemas, full audit log. The server is the boundary — the engine remains the authority on physics, collision, scoring, and multiplayer state.
The Raku engine is modular with subsystems covering rendering, physics, audio, AI, XR, networking, animation, and more. Adapters plug in over the MCP boundary; the engine retains deterministic authority.
Full API documentation and subsystem details are available under NDA. Request access →
Add the RakuAI MCP server to Claude Desktop, Cursor, or any MCP-capable client. The 17 native tools appear natively in your conversations. Drive the runtime from the assistant you already use.