Exaro Studio docs

There are two ways to use the plugin, and they share the same tools and the same approval queue. The chat panel runs inside the editor and talks to a provider you pick. The MCP server lets an outside assistant — Claude Code, Claude Desktop, Cursor — drive the running editor over localhost.

What works today

Everything below is in the shipping build and is exercised on a real project before each release. If a page describes something that is still landing, it says so inline.

• In-editor chat panelWorks today — dockable at Window → Exaro Studio (or Ctrl+Alt+A). Claude, Gemini, OpenAI, OpenRouter, and local models via Ollama.
• Bring your own keys, or your own CLIWorks today — use an API key, or reuse the claude / gemini / codex subscription CLI you already pay for. The Send button tells you which route you are about to take, and whether it bills.
• MCP serverWorks today — JSON-RPC 2.0 over Streamable HTTP on http://127.0.0.1:8765/mcp, loopback only, on its own thread.
• Approval queueWorks today — all 215 mutating tools build a preview first, block on your decision, then apply inside one undoable transaction.
• Local-first asset generationWorks today — text to 3D mesh, texture, and audio on your own GPU, no API tokens. Cloud backends are opt-in.
• Component storeWorks today — buy a game system (save/load, inventory, character kit) and let the agent install it into your project under one approval.

What is still in progress

• Unreal Engine 5.8 supportIn progress — 5.8 ships its own experimental MCP server. Exaro Studio runs alongside it on a separate port. See the 5.8 guide.
• Searchable docsIn progress — you are reading the first cut. The tool reference is generated from the plugin source, so it can never drift from the build.

Start here