How to Build Roblox Games With Claude: Studio MCP Setup Guide

To build Roblox games with Claude, turn on Roblox Studio’s built-in MCP server (Assistant > … > Manage MCP Servers > Enable Studio as MCP server). Then connect Claude Code or Claude Desktop through Studio’s quick connect option. Once you’re connected, Claude can read your place, write and edit scripts, run Luau, insert or generate assets, and playtest your game. You describe what you want and review what it does.

The rest of this guide covers the setup, a practical workflow, and a file-based alternative for bigger projects. Everything here reflects Roblox and Anthropic documentation as of November 2026. Both products change quickly, so expect menu names and tool lists to shift.

How Claude talks to Roblox Studio

The bridge is the Model Context Protocol (MCP), an open standard that lets AI apps call tools in other programs. According to Roblox’s MCP documentation, the Studio MCP server is built into Studio. It runs as a local process on your machine and talks to your AI client over stdio (standard input/output). Any MCP client that supports stdio can use it, and Claude Desktop and Claude Code are both on the officially supported quick connect list.

If you’ve seen older tutorials, you may have read about installing a separate Rust binary and Studio plugin. That project, Roblox/studio-rust-mcp-server, is now archived. Its README says it is no longer actively developed and points users to the MCP server built into Studio. Use the built-in server for new projects.

What Claude can do once connected

Roblox groups the built-in server’s tools like this:

This is the important part: Claude isn’t just pasting code into a chat. It can test its own work by playtesting, reading the console, and fixing errors.

Step-by-step setup

1. Get the prerequisites

Roblox only lists two requirements: the latest version of Roblox Studio and an MCP client installed on the same computer. For Claude, that means Claude Desktop or Claude Code. Update Studio before you start, because an older build may not have the MCP menu.

2. Enable the MCP server in Studio

1. Open a place in Roblox Studio.
2. Open Assistant.
3. Click the … menu and choose Manage MCP Servers.
4. Turn on Enable Studio as MCP server.

The panel then shows the quick connect option and per-client setup instructions.

3. Connect Claude with quick connect

1. In the same panel (Assistant Settings > MCP Servers), expand Quick connect.
2. Turn on Claude Code or Claude Desktop.
3. Restart the Claude app.

If your client isn’t listed, Roblox says to install it and then restart Studio so it can detect it.

4. Or connect manually

For Claude Desktop, add the Roblox_Studio entry from Roblox’s docs to your MCP config file. On macOS the entry looks like this:

{
  "mcpServers": {
    "Roblox_Studio": {
      "command": "/Applications/RobloxStudio.app/Contents/MacOS/StudioMCP"
    }
  }
}

On Windows, Roblox’s version uses "command": "cmd.exe" with the arguments "/c" and "%LOCALAPPDATA%\\Roblox\\mcp.bat". If the file already lists other servers, add only the Roblox_Studio entry inside your existing mcpServers block, and check your commas. Roblox notes that a missing comma will stop the whole config from loading.

For Claude Code, the Claude Code MCP docs give the syntax claude mcp add --transport stdio <name> -- <command> [args...]. Combined with Roblox’s macOS command, that looks like this:

claude mcp add --transport stdio Roblox_Studio -- /Applications/RobloxStudio.app/Contents/MacOS/StudioMCP

On Windows, quick connect is the simplest route. If you configure it by hand, use the Windows command from Roblox’s docs. Replace %LOCALAPPDATA% with your real path if your shell doesn’t expand it. You can also paste the JSON entry with claude mcp add-json.

5. Verify the connection

• In Studio, open Manage MCP Servers again. A green indicator under Enable Studio as MCP server shows how many clients are connected.
• In Claude Code, run claude mcp list, or type /mcp inside a session to see the server’s status and tool count.

If the tools don’t appear, Roblox’s troubleshooting steps are to restart both Studio and the client, confirm that the command path exists, and validate your JSON.

A workflow that actually works

Once Claude is connected, the quality of your results depends mostly on how you scope the work. Here’s a loop that works well:

1. Start with exploration. Ask Claude to look through the place and summarize what’s there before you change anything, for example: “Use search_game_tree and tell me which scripts handle the round system.” This gives it real context instead of guesses.
2. Ask for one feature at a time. “Add a checkpoint system: touching a SpawnLocation-style pad saves the player’s stage, and they respawn there” is a good-sized request. “Make me a simulator game” is not.
3. Say where code should live. Roblox code runs as server Scripts, client LocalScripts or shared ModuleScripts. Tell Claude what belongs on the server, especially anything that touches currency, stats or data saving.
4. Let it playtest. Ask Claude to start play mode, check the console output and fix any errors it finds. The screen_capture and input simulation tools let it check things visually too.
5. Review before you keep it. Read the scripts it wrote, playtest yourself, and only then save and publish from Studio.

If you have several Studio windows open, have Claude call list_roblox_studios first. Every tool call takes a studio_id, so it can target the right place.

For bigger projects: files, Git and Claude Code

The MCP server edits your place directly. That’s fine for prototypes, but on a serious project you’ll want your code in version control so you can review diffs and undo bad edits. Roblox documents two official ways to put your scripts on disk, where Claude Code can also work with them as normal files.

Roblox notes that Script Sync only syncs Scripts, LocalScripts, ModuleScripts and Folders. It also warns against syncing scripts that have attributes or tags, because those can be lost. For Rojo, Roblox’s third-party tools page suggests installing it with the Rokit toolchain manager and then running rojo plugin install, rojo init, and rojo serve. Roblox also points out that Rojo isn’t maintained by Roblox and can change at any time.

A practical combination is to keep scripts in a Git repo through Script Sync or Rojo and have Claude Code edit those files. Leave the MCP connection on so Claude can still playtest and inspect the live place.

Limits and cautions

• Security: Roblox’s docs warn that MCP clients can read and modify content in your open places. Only connect clients you trust, and stick to the official setup above rather than unofficial MCP servers.
• Back up first: Work on a copy of your place, or commit to Git before big changes.
• AI output still needs review: Claude can write Luau that runs but has design flaws, such as trusting the client with values the server should check. Test multiplayer behavior yourself.
• Costs and plans: Claude Desktop and Claude Code use your Anthropic account. Check Anthropic’s current plans, because usage limits and pricing change.
• Things change: The tool list above comes from Roblox’s documentation as of November 2026. Check the official MCP page for the latest.