How to connect Claude, Cursor or ChatGPT to Roblox Studio with MCP

What the Studio MCP server does

MCP (Model Context Protocol) is an open standard that lets AI tools talk to other applications. Roblox builds an MCP server into Studio. When it is on, an AI client on your computer can explore the place you have open, read and write scripts, run Luau and test the game in play mode, all through tools the server exposes.

The server runs as a local process on your machine and talks to the client over stdio (standard input and output). Nothing happens on its own: every action starts as a request from your client, and the client decides which tool to call. You need the latest version of Roblox Studio and the MCP client you want to use, both installed on the same computer.

Two ways to use Claude or GPT with Studio

This guide is about the first route. If all you want is a Claude or OpenAI model answering inside Studio, the second is shorter: get an API key from the provider, open Assistant, click … > Manage API Keys, choose the provider, paste the key, and select the model in the Model drop-down.

Step 1: Turn on the MCP server in Studio

1. Open Roblox Studio and open a place. If Studio offers an update, install it first: the server needs the latest version.
2. Click Assistant at the top right of Studio (the right side of the mezzanine bar) to open the Assistant window.
3. Click … and choose Manage MCP Servers.
4. Turn on Enable Studio as MCP server.

The panel now shows a Quick connect option and setup instructions for different clients. Keep it open. You need it for the next step, and it is where the connection indicator appears.

Step 2: Connect your AI client

Roblox gives three ways to connect, in this order: quick connect if your client is on the list, a JSON configuration if the client reads MCP config files, and a CLI command for clients that need one.

Quick connect

Quick connect supports seven clients (as listed on 30 September 2026): Antigravity, Codex CLI, Claude Code, Claude Desktop, Cursor, Gemini CLI and Visual Studio Code.

1. In the panel from Step 1 (Assistant Settings > MCP Servers), expand the Quick connect drop-down. It lists the supported clients that are installed on your computer.
2. Turn on the client you want.
3. If your client is missing from the list, install it and restart Roblox Studio. If you installed it while Studio was open, you may need to restart Studio, the client, or both.

Setup by client

Roblox's coding harness guide pairs the MCP connection with an editor: Cursor, or Visual Studio Code with an extension such as Claude Code. If you want the agent to write code as files as well as drive Studio, see Script Sync and Git below.

Other clients: JSON config or CLI command

The server works with any client that supports stdio transport. If yours has no quick connect, add Roblox Studio to its MCP configuration. These are the complete configurations Roblox documents. If Roblox Studio is your only MCP server, use them exactly as they are.

{
  "mcpServers": {
    "Roblox_Studio": {
      "command": "cmd.exe",
      "args": [
        "/c",
        "%LOCALAPPDATA%\\Roblox\\mcp.bat"
      ]
    }
  }
}

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

Where the config file lives depends on the client (Roblox's example calls it mcp.json). Roblox's instructions say to finish setup with your client's own documentation, then restart the client so it picks up the change.

CLI command

Some clients take a command instead of a config file. This is the command that starts the server, for you to register the way your client's documentation describes:

cmd.exe /c %LOCALAPPDATA%\Roblox\mcp.bat

/Applications/RobloxStudio.app/Contents/MacOS/StudioMCP

Both point at a file that Studio installs. On Windows, %LOCALAPPDATA% is your user's local app data folder. On macOS, the path runs inside RobloxStudio.app in /Applications. If the file is not there, the client cannot start the server: see Troubleshooting.

Step 3: Check the connection

1. In Studio, open Assistant and click … > Manage MCP Servers.
2. Under Enable Studio as MCP server, look for the green indicator. It shows the number of connected clients.
3. In your client, start with a request that only reads, so a wrong setup cannot change anything. For example: Using the Roblox Studio MCP tools, list what is in Workspace. Do not change anything.

On a fresh Baseplate the answer should list the default Camera, Terrain, Baseplate and SpawnLocation. Your client may ask you to approve the tool call, or offer to add the tool to an allowlist. Approving it once is enough for this test.

What about ChatGPT?

As of 30 September 2026, Roblox's documentation does not describe connecting ChatGPT to Studio, and ChatGPT is not on the quick connect list. This is what is and is not covered.

• Documented: Codex CLI, OpenAI's command-line coding agent, is a quick connect client. Set it up like the others in Step 2. OpenAI's Codex documentation offers Sign in with ChatGPT the first time you run it, so this is the closest documented way to bring a ChatGPT account to Studio.
• Documented: Assistant accepts an OpenAI API key. Open Assistant, click … > Manage API Keys, choose OpenAI, paste the key and pick a model. Assistant then uses that model inside Studio.
• Not documented: the ChatGPT app or website. Roblox says the server works with any client that supports stdio transport, so if an OpenAI app you use can add a local stdio MCP server, the JSON configuration or command above is what it needs. Whether it can is a question for OpenAI's documentation, not Roblox's.

Copying code from a ChatGPT chat into a Script still works, but nothing on that route reads your place or checks the result in Studio. The guide to using AI in Roblox Studio compares the options side by side.

What tools the server gives your client

Roblox lists 26 tools in eight groups (as of 30 September 2026). Your client chooses which to call; you do not call them by hand. Every call carries a studio_id that names the Studio window it targets.

Two kinds of tool deserve attention. First, the ones that change things: multi_edit and execute_luau change your place directly, insert_asset brings outside content into it by asset ID, and upload_image sends images to Roblox's asset server. Second, the playtest tools, which let an agent check its own work: Roblox's StudioTestService reference says start_stop_play starts a single Play Client session, and the input tools drive the character while it runs.

Roblox also routes other Studio features through the server: Scene Analysis data through SceneAnalysisService, MicroProfiler analysis, control of the Device Simulator, and an AI skill that converts a game to streaming.

Working with more than one Studio window

One client can connect to several running Studio windows at once. Because every tool call names its target with studio_id, the agent has to know which window you mean. It can call list_roblox_studios to see each window's name, Studio instance ID and place ID. Local places with no place ID are listed by name only, and when two windows share a name, the place ID tells them apart.

In practice: name the place in your prompt, and close any place you do not want touched. The server can reach every open place, not only the one you are looking at.

Work safely: back up, approve, review

Roblox's own warning is short: MCP clients can read and modify content in your open places, so connect only clients you trust. With tools that run code, insert assets and start playtests, one misread instruction can do real damage. These habits keep it recoverable.

• Save a version before each session. File > Save to Roblox with Notes (Ctrl+Alt+S, or Cmd+Option+S on Mac) creates a named checkpoint. To go back, open Window > Version History, click ⋮ next to that version, choose Open Local Copy, then use File > Save to Roblox As in the copy to restore it over the place. File > Save to File keeps a copy on your computer as well.
• Do not count on Ctrl+Z. Roblox's MCP page does not say whether a client's edits land in Studio's undo history, so treat your saved version as the way back.
• Work in a test copy, not the live game. With Enable Studio Access to API Services on (File > Experience Settings > Security), Studio reads and writes the same data stores as your live game, and Roblox advises turning it on only for a separate test version. That includes code an agent runs and playtests it starts.
• Keep approvals on for tools that change things. Allowlisting read tools such as script_read and search_game_tree is low risk. Keep approving multi_edit, execute_luau, insert_asset and upload_image call by call until you trust the workflow.
• Review before you keep it. Read the scripts it changed, check the Explorer for new or missing objects, and playtest yourself. An agent's playtest shows what it chose to check, not everything a player will do.

For bigger projects: Script Sync and Git

Roblox's coding harness guide adds two pieces to the MCP connection. Script Sync links Studio services to folders on disk, so your editor and agent work on .luau files that appear in Studio as scripts. Git then records each change you commit, which gives your code a history and a way back that does not depend on Studio.

1. The coding harness guide treats Script Sync as a beta: choose File > Beta Features, enable Script Sync, click Save, and restart Studio when asked. Roblox's main Script Sync page does not mention a beta, so if Script Sync already appears when you right-click a service in the Explorer, skip this step.
2. In the Explorer, right-click ServerScriptService, choose Script Sync > Sync to, and pick your project folder: the top-level folder that holds folders named after each service, not one of the folders inside it. Repeat for ReplicatedStorage and StarterPlayerScripts.
3. Commit a clean state before you ask the agent for anything big.

git add .
git commit -m "Checkpoint before agent session"

Script Sync covers the scripts in those services. The MCP connection covers what it cannot reach, such as StarterGui and StarterPack, along with playtests and the Output.

Troubleshooting: when the client will not connect

Roblox's own checklist has three items: restart both Studio and the client, check that the command or binary path is correct and the file exists, and check the JSON syntax. These are the situations behind it.

Or skip the MCP setup: RoCode

RoCode (RoCode.app) is a different route, and it is not an MCP product. It is an independent AI agent for Roblox Studio: you describe a change in a web chat at rocode.app, and a free RoCode plugin from the Creator Store carries out the steps in the place you have open. There is no config file, command line or MCP server to set up. You pair the chat and the plugin once with the 8-character code shown in the plugin panel, and allow the plugin's HTTP and Script Injection permissions in Studio.

The trade-offs, stated plainly. RoCode cannot connect a Claude, Claude Code or ChatGPT subscription: it runs third-party models through OpenRouter as RoCode v3.3, v3.6 and v4.0. It does not run code in Studio, start playtests, insert Creator Store models or generate meshes, all of which the Studio MCP tools above can do. The free Starter plan includes 250,000 tokens a day. For how it compares with other tools, see Roblox AI tools compared.

RoCode does not start playtests, so press Play yourself to confirm the fix. How the plugin and pairing work. RoCode is an independent product, not affiliated with or endorsed by Roblox Corporation.

Questions

Sources and further reading

• Roblox Creator Docs: Connect to the Roblox Studio MCP server. enabling the server, quick connect, JSON and CLI setup, the tool list, multiple Studio windows and troubleshooting
• Roblox Creator Docs: MCP servers (Assistant). using your own Anthropic, OpenAI or Google API key in Assistant
• Roblox Creator Docs: Build with a coding harness. Script Sync, MCP with Cursor or Visual Studio Code, and Git
• Roblox Creator Docs: Version History. saving with notes and restoring a previous version
• Roblox Creator Docs: Data stores. why Studio access to API services belongs on a test copy
• Roblox Engine API: StudioTestService. how the start_stop_play tool compares with scripted multi-client tests
• OpenAI: Codex CLI. signing in to Codex CLI, including Sign in with ChatGPT
• Model Context Protocol: Introduction. the open standard the Studio server implements