Guide · AI in Roblox Studio

How to use GitHub Copilot with Roblox Studio

GitHub Copilot does not open a Roblox place, but Copilot in Visual Studio Code can use MCP servers, and Roblox Studio has one built in. Connect the two and Copilot can read your place, edit scripts, run Luau and start playtests in the Studio window you have open. Roblox lists Visual Studio Code as a quick connect client but never mentions Copilot, and VS Code changed where Copilot keeps its MCP servers in 2026, so the details matter. This guide follows Roblox's, VS Code's and GitHub's documentation as read on 13 November 2026. For syncing scripts to files in the same editor, see how to use Cursor or VS Code with Roblox Studio.

Updated 13 November 202613 min readBeginnerWindows and macOSWritten by

In short

In Roblox Studio, open Assistant, click … > Manage MCP Servers and turn on Enable Studio as MCP server. In VS Code, with Copilot set up and Copilot chosen in the Session Target drop-down, run Chat: Open Customizations, select MCP Servers > Add Server (+), choose Command (stdio), enter Roblox's command, give it a server ID, and select Global > Copilot Global. Then ask Copilot for something that only reads, and expand the tool call to confirm it used Studio.

  • Roblox's Quick connect has a Visual Studio Code switch, but Roblox does not say which file it writes. VS Code now has two families of MCP files, and Copilot sessions read only one of them, so check that the server shows up in Copilot.
  • GitHub's plans page lists MCP as included on Copilot Free, Student, Pro, Pro+ and Max. On Copilot Business and Enterprise, an administrator has to enable the MCP servers in Copilot policy, which is off by default.
  • Keep Copilot on Manual permissions and approve Studio tool calls one at a time. A connected client can edit scripts, run code, start playtests and save the place.
On this page
  1. What you need
  2. 1. Turn on the server
  3. 2. Add the server
  4. 3. Check it works
  5. 4. Approvals
  6. Scripts as files
  7. Troubleshooting
  8. Or skip the setup
  9. Questions
  10. Sources

What you need before you start

Requirements, from Roblox's, VS Code's and GitHub's documentation, 13 November 2026
You needDetails
Roblox StudioThe latest version, on Windows or macOS. The MCP server is built into Studio.
Visual Studio CodeOn the same computer as Studio. GitHub's MCP page asks for VS Code 1.99 or later; update to the current release, because the steps below use menus from 2026.
GitHub Copilot, set up in VS CodeHover over the Copilot icon in the Status Bar, select Use AI Features and sign in. VS Code says that without a plan, signing in enrolls an eligible account in Copilot Free.
A plan that allows MCPGitHub lists MCP as included on Copilot Free, Student, Pro, Pro+ and Max. On Business and Enterprise the MCP servers in Copilot policy must be enabled by an administrator; GitHub says it is disabled by default.
A local folder open in VS CodeVS Code's MCP page lists opening a local project folder as a prerequisite. Use the folder where you keep your game's files, or make an empty one.

GitHub's plans page describes Copilot Free as limited access with automatic model selection, and gives no monthly figure for agent work. Models you reach through Copilot use AI credits from your plan; VS Code shows your usage in the Copilot status dashboard in the Status Bar.

What Roblox says about VS Code

Roblox's MCP page lists Visual Studio Code among seven quick connect clients and does not mention GitHub Copilot anywhere. Its coding harness guide says VS Code needs an AI extension and uses Claude Code as its example. Copilot fills the same role: it is the agent inside the editor that calls the MCP tools. So the Roblox half of this guide is documented by Roblox, the Copilot half by VS Code and GitHub, and nobody documents the two together.

Step 1: Turn on the MCP server in Studio

  1. Open Roblox Studio and open the place you want to work on. Install any Studio update first.
  2. Click Assistant to open the Assistant window.
  3. Click … and choose Manage MCP Servers.
  4. Turn on Enable Studio as MCP server.

Keep the panel open: the connection indicator appears here. If the Assistant button is missing, see how to open the Assistant panel.

Step 2: Add the Studio server to Copilot

Why the file matters in 2026

VS Code runs agents in what it calls harnesses. The Copilot harness is the current one. The older Local harness is deprecated, and VS Code says it will be removed in February 2027. Each reads different MCP files, and older tutorials, including GitHub's own MCP page, still describe the older file.

MCP configuration files in VS Code, from VS Code's MCP configuration reference, 13 November 2026
FileTop-level keyRead by
~/.copilot/mcp-config.json (Copilot user file; $COPILOT_HOME/mcp-config.json if that variable is set)mcpServersCopilot sessions. Shared across your workspaces and with Copilot CLI on the same computer.
.mcp.json at the workspace rootmcpServersCopilot sessions, for that workspace. Meant to be shared through source control.
.vscode/mcp.json in the workspaceserversThe deprecated Local harness. VS Code says not to use it for new Copilot setups.
mcp.json in your VS Code user profileserversThe deprecated Local harness.

The Copilot files use the same mcpServers shape as Roblox's own configuration. The Local harness files use servers and require "type": "stdio" on a local server.

Add it through the guided flow

This is the route VS Code documents for a server you add by command. It writes the Copilot user file for you.

  1. Open the Chat view and select Copilot in the Session Target drop-down.
  2. Run Chat: Open Customizations from the Command Palette (Ctrl+Shift+P, or Cmd+Shift+P on Mac) and select MCP Servers.
  3. Select Add Server (+) in the User group.
  4. Choose Command (stdio) and enter Roblox's command for your system (below).
  5. Enter a unique server ID, for example robloxStudio.
  6. Select Global, then Copilot Global.
  7. Review any trust request VS Code shows before you accept it. It is asking whether this command may run on your computer.
Command · macOS
/Applications/RobloxStudio.app/Contents/MacOS/StudioMCP
Command · Windows
cmd.exe /c %LOCALAPPDATA%\Roblox\mcp.bat

Or write the file yourself

If the guided flow does not take the Windows command cleanly, edit the Copilot user file directly. This is Roblox's configuration with one added line: VS Code's reference lists type for stdio servers, and Roblox's JSON has none, so the examples include it. The reference does not say whether the portable format requires it.

mcp-config.json in the .copilot folder of your user profile · Windows
{
  "mcpServers": {
    "robloxStudio": {
      "type": "stdio",
      "command": "cmd.exe",
      "args": [
        "/c",
        "%LOCALAPPDATA%\\Roblox\\mcp.bat"
      ]
    }
  }
}
~/.copilot/mcp-config.json · macOS
{
  "mcpServers": {
    "robloxStudio": {
      "type": "stdio",
      "command": "/Applications/RobloxStudio.app/Contents/MacOS/StudioMCP"
    }
  }
}

Do not commit a Studio entry in a shared .mcp.json if your team uses both Windows and macOS: the two commands differ. The personal file avoids that.

What about Roblox's quick connect switch?

In Studio's Manage MCP Servers panel, the Quick connect drop-down lists Visual Studio Code if it is installed, and Roblox's coding harness guide turns that switch on. Roblox does not say which of the four files the switch writes. If it writes one of the Local harness files, a Copilot session will not see the server. So try it if you like, then check: run Chat: Open Customizations with Copilot as the session target and look under MCP Servers. If Studio is not there, add it with the guided flow, and remove the duplicate if you later find one.

Using the Claude Code or Codex extension in VS Code instead of Copilot? Those extensions keep their own MCP configuration. See Claude Code and OpenAI Codex.

Step 3: Check the connection

  1. Run MCP: List Servers from the Command Palette, or open Chat: Open Customizations > MCP Servers. The Studio server should be listed. Its … menu has Start Server, Stop Server, Restart Server and Show Output.
  2. In Studio, open Assistant > … > Manage MCP Servers. A green indicator under Enable Studio as MCP server shows the number of connected clients.
  3. In a Copilot chat, send a first request that cannot change anything.
Prompt
Use the Roblox Studio MCP tools. Call list_roblox_studios and tell me which place you are connected to, then list what is in Workspace. Do not change anything.

On a fresh Baseplate, Roblox's coding harness guide expects the answer to describe the default Camera, Terrain, Baseplate and SpawnLocation, and notes that you might need to approve the command. Then expand the tool call in the conversation. VS Code's own advice applies here: a plausible answer without a tool call does not verify the connection.

Step 4: Keep Copilot asking before it changes your place

VS Code's warning is direct: local MCP servers can run code on your machine, and tools can act with your permissions. Roblox's is similar: MCP clients can read and modify content in your open places. With Studio connected, the tools that matter are multi_edit (edits and creates scripts), execute_luau (runs code in Studio), start_stop_play (starts a playtest), insert_asset, upload_image, the generate_ tools and save_place, which saves the open place without a dialog.

  • Stay on Manual permissions. It is the default level for Copilot sessions. Tools that need confirmation show a dialog, and the default choice is Allow Once. The drop-down also offers session-wide and Always Allow choices.
  • Do not pick Allow all or Autopilot while Studio is connected. VS Code shows a warning the first time you select either, for good reason. Assisted permissions hands each tool call to a model to judge instead of to you, which is also not what you want for a tool that runs code in your place.
  • Be selective with Always Allow. Chat: Manage Tool Approval lists tools grouped by source, such as an MCP server. Ticking the top-level box for the Studio server trusts every Studio tool at once, including the ones that run code and save. Tick only tools that read, such as script_read, search_game_tree, inspect_instance and get_console_output.
  • Undo approvals when in doubt. Chat: Reset Tool Confirmations clears all saved approvals. MCP: Reset Trust resets the decision to let a server start, which is a separate thing.
  • Limit the server's tools. VS Code says a server in the Copilot configuration can carry a tools list that selects which tools are available, and that this does not replace the approval policy.

Save a version before each session

Roblox's MCP page does not say whether a client's edits land in Studio's undo history. Before Copilot changes anything, use File > Save to Roblox with Notes so there is a named version to return to, and work in a test copy rather than your live game. The Studio MCP guide shows how to restore a version. One client can reach every open Studio window, and each tool call names its target with a studio_id, so close the places you do not want touched.

Copilot and your scripts as files

MCP is one of two documented ways to bring an editor to Roblox. The other is syncing scripts to .luau files on disk, with Studio's Script Sync or the community tool Rojo. Copilot is at home with files: it edits them in the editor, you see the diff, and Git keeps the history. The MCP tools then cover what is not a script, such as GUIs, RemoteEvents, parts, playtests and the Output.

Know this before you combine them: Script Sync applies a saved file change to Studio straight away, so accepting a Copilot edit to a synced file is accepting it into your place. Commit a clean state first. The setup for Script Sync and Rojo, the file naming rules and the Luau language server are in how to use Cursor or VS Code with Roblox Studio.

Where Copilot cannot reach Studio

  • The Cloud session target. VS Code describes it as the Copilot harness running in a managed cloud environment. Studio's server is a local process on your computer, so a cloud session has nothing to start.
  • Copilot Chat on GitHub.com and GitHub Mobile. These run in a browser or on a phone, not on the computer where Studio runs.
  • A remote window. VS Code says a local Copilot user file is not forwarded to a remote host. Work in a local window on the Studio computer.

Troubleshooting Copilot and Studio

Roblox's own checklist has three items: restart both Studio and the client, check that the command or binary path exists, and check the JSON syntax. VS Code adds its own. These are the cases you are likely to meet.

I turned on Visual Studio Code in Quick connect, but Copilot has no Roblox tools

Roblox does not say which file its switch writes, and Copilot sessions read only the Copilot user file and a workspace-root .mcp.json. Open Chat: Open Customizations > MCP Servers with Copilot as the session target. If Studio is not listed, add it with the guided flow in Step 2.

I followed an older guide and put the server in .vscode/mcp.json

That file uses the servers key and belongs to the Local harness, which VS Code has deprecated and plans to remove in February 2027. It still works in a Local session where your organization allows one. For Copilot sessions, add the server to the Copilot user file instead.

The server will not start

Open the server's … menu and choose Show Output to read its log. Check that the file exists: %LOCALAPPDATA%\Roblox\mcp.bat on Windows, /Applications/RobloxStudio.app/Contents/MacOS/StudioMCP on macOS. Open your place in Studio, make sure Enable Studio as MCP server is on, then stop and start the server.

VS Code blocks the server from starting

A workspace file such as .mcp.json inherits Workspace Trust, and Restricted Mode stops its servers from starting. Trust the folder, or use the personal Copilot file. If you declined a trust prompt by mistake, run MCP: Reset Trust.

MCP is unavailable or greyed out on a work or school account

On Copilot Business and Enterprise, GitHub's MCP servers in Copilot policy is disabled by default, and organizations can also apply an allowlist that local configuration cannot override. Ask your administrator. GitHub says the policy does not govern Copilot Free, Pro, Pro+ or Max accounts.

The server runs but Copilot never calls a tool

Name the server and tool in your request, as in the prompt in Step 3, and confirm the session target is Copilot. VS Code's chat debug view shows whether a tool was offered and called.

Copilot changed the wrong place

With several Studio windows open, every tool call names its target with a studio_id. Ask Copilot to call list_roblox_studios and name the place you mean, close the windows you are not using, and restore the changed place from Version History.

Or skip the MCP setup: RoCode

Copilot with MCP suits people who already work in a code editor. 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 allow the plugin's HTTP and Script Injection permissions in Studio. The plugin then connects by itself when Studio is signed in to the same Roblox account you use on RoCode; otherwise you pair the chat and the plugin once with the 8-character code shown in the plugin panel.

The trade-offs, stated plainly. RoCode runs its own choice of third-party models through OpenRouter under their own names: GPT-6 Luna on every plan, GLM 5.3 Flash and Claude Sonnet 5.5 from Pro, Claude Opus 5.5 from Studio and GPT-6 Astra from Ultra. With plugin 3.9 or newer it can run a short playtest and read the errors, and with plugin 3.9.11 or newer control a test character to check the game works. It does not run code directly or generate meshes, both of which the Studio MCP tools can do. The free Starter plan includes 1 credit a day. For how it compares with other tools, see Roblox AI tools compared.

You type

I just playtested and got an error in RoundManager. Find the cause and fix it.

RoCode does
  • Reads the Output from the playtest you ran with Check Output, including Server and Client lines, then opens the script around that line with Read Script
  • Fixes the failing code in place with Edit Script, in the Studio window that is connected
  • Compile-checks the script inside Studio with Check Script before it finishes. That is a compile check, not a type check or a playtest
  • Sends its changes in batches, and each batch is an undo point in Studio's own history

RoCode checks only what it chose to test, so press Play yourself and play a round to confirm the fix. How the plugin and pairing work. RoCode is an independent product, not affiliated with or endorsed by Roblox Corporation.

Questions

Can GitHub Copilot connect to Roblox Studio?

Yes, through Copilot in Visual Studio Code and the MCP server built into Studio. Turn on Enable Studio as MCP server under Assistant > … > Manage MCP Servers, then add Studio as a Command (stdio) server in VS Code under Chat: Open Customizations > MCP Servers. Roblox lists Visual Studio Code for quick connect but does not mention Copilot, and we have not run the pair end to end.

Does Copilot Free work with the Roblox Studio MCP server?

GitHub's plans page lists MCP as included on Copilot Free (checked 13 November 2026). It describes the Free plan as limited, with automatic model selection, and gives no figure for how much agent work it covers. Roblox's MCP page mentions no charge for the Studio server.

Where does VS Code keep the MCP config for Copilot?

For Copilot sessions, in ~/.copilot/mcp-config.json for your user, or a .mcp.json at the workspace root. Both use a top-level mcpServers object. The older .vscode/mcp.json with a servers key belongs to the Local harness, which VS Code has deprecated.

Does Copilot in Visual Studio or JetBrains work too?

GitHub documents MCP for those editors as well, but Roblox's quick connect list names only Visual Studio Code from that family, and this guide covers only VS Code. Any client that can start a stdio server can use the command Roblox documents; the Studio MCP guide has it.

Can Copilot playtest my Roblox game?

Through the Studio MCP tools, yes. start_stop_play starts and stops a playtest, get_console_output reads the Output, screen_capture captures the viewport, and the input tools move the character and send keys and clicks. It checks only what it chose to check, so play the game yourself before you publish.

Do I still need Rojo or Script Sync?

Not for MCP. The Studio tools read and edit scripts inside the place directly. Script Sync or Rojo is worth adding when you want your scripts as files that Copilot edits in the editor and Git tracks. The two work side by side.

Sources and further reading

Try RoCode on your own place.

Free every day, no card required. Install the plugin, describe the feature, and review what lands in Studio.