Build Roblox games with Claude: Studio MCP, Claude Code and where 3D models come from

What changed in 2026

Until 2025, using Claude for Roblox meant copying Luau out of a chat window. Then Roblox shipped an open-source Studio MCP server (May 2025), added playtest tools (February 2026), and in March 2026 built the MCP server into Studio itself. The open-source repository is now archived in favour of the built-in one.

So now Claude can work in your place. It explores the data model, creates instances, writes scripts, starts a playtest, reads the console output and fixes what broke.

The setup Roblox recommends

Roblox's own guide, Build with a coding harness, uses Claude Code as one of its two example agents. The pieces are:

1. Claude Code, in VS Code or a terminal, signed in with your Anthropic account.
2. A project folder in Git, with ServerScriptService/, ReplicatedStorage/ and StarterPlayerScripts/ holding .luau files.
3. Script Sync (a Studio beta), which links each service in Studio to its folder on disk, so files the agent writes appear as scripts in Studio.
4. The Studio MCP server, for what Script Sync can't reach, such as StarterGui and StarterPack, and for running and testing.

To connect, open Assistant in Studio, choose … ⟩ Manage MCP Servers, turn on Enable Studio as MCP server, and enable your client under Quick connect. Claude Code and Claude Desktop are both listed (Studio MCP docs).

Roblox also publishes an official Roblox Studio plugin for Claude. In Claude Code, run /plugin, search for Roblox Studio and install it, then ask Claude to get you set up. Studio's MCP server runs on your computer, so claude.ai in a browser can help you plan and write Luau but can't connect to Studio.

What Claude does well here

• Systems and glue code: rounds, waves, leaderboards, shops, data saving, remote events across client and server.
• Test and fix loops: start a playtest, read the output, patch, repeat.
• Bulk edits: rename, re-parent or re-configure hundreds of instances.
• Reading code you didn't write, including that free model's scripts. See Roblox 3D assets for what to look for.

Where it needs you

• Art direction. The agent can insert Creator Store models and call Roblox's own generation tools, but it can't tell which assets make your game look like your game.
• Reviewing changes. MCP clients can read and modify your open place, so Roblox advises connecting only clients you trust. Commit before big requests so you can roll back.
• Policy. You are responsible for what ships, AI-made or not. See are AI models allowed on Roblox?

The 3D asset gap, and how to fill it

Claude writes Luau. It doesn't sculpt your hero props. Over MCP it can reach the Creator Store and Roblox's own mesh generation, which is fine for placeholders and filler. For assets that define your game's look, you want control over the input, such as a sketch of the exact silhouette, and the chance to review the mesh before it enters your place.

That's the split that works in practice:

• Claude builds and tests the systems, inside Studio, over MCP.
• Vi3W makes the custom models: prompt, photo or sketch in, automatic retopology to low poly, GLB, FBX or OBJ out.
• You import the meshes (File ⟩ Import), then ask Claude to wire them up, by spawning them, adding collision or attaching scripts.

The step-by-step for the asset side is in how to make Roblox models with AI. Make your game's first custom prop in Vi3W.