Vi3W
Skip to content

Guides

Use Cursor with Roblox Studio: MCP and Rojo setup

Set up Cursor for Roblox development: connect it to Studio's MCP server, sync scripts with Rojo, and the workflow that combines both.

3 min read

A glowing cursor arrow connected by a beam of light to a low-poly game island
Illustration. An editor connected to a live place.

Quick answer

Can you use Cursor with Roblox Studio?

Yes, in two ways that work well together. Connect Cursor to Studio's built-in MCP server through Studio's quick connect, so its agent can read and edit your open place and playtest it. Or keep your scripts as files with Rojo, edit them in Cursor, and sync them into Studio.

Route 1: Cursor talks to Studio over MCP

Roblox Studio has a built-in MCP server, and Cursor is in its quick-connect list (Studio MCP).

  1. Install the latest Roblox Studio and Cursor.
  2. In Studio, open Assistant ⟩ … ⟩ Manage MCP Servers and turn on Enable Studio as MCP server. A green indicator shows connected clients.
  3. Under Quick connect, turn on Cursor. If Cursor isn't listed, install it and restart Studio.
  4. In Cursor, check the MCP settings show the Roblox Studio server as connected.
  5. Open a place in Studio and ask Cursor's agent something like "list the scripts in ServerScriptService".

If you configure it by hand, the server is a local command (stdio). On macOS it's /Applications/RobloxStudio.app/Contents/MacOS/StudioMCP. On Windows it's cmd.exe /c %LOCALAPPDATA%\Roblox\mcp.bat.

Through MCP, Cursor's agent gets Studio's tools: reading and editing scripts, searching the game tree, running Luau, starting playtests, reading the console and taking screenshots.

A glowing arrow cursor and a floating code-bracket shape linked by light to a cube
Illustration. The editor's agent reaches into Studio through the MCP server.

Route 2: scripts as files with Rojo

Rojo syncs a folder of .luau files on your computer into Studio. With it:

  • Your scripts live in a normal project folder, so Cursor's indexing, search and multi-file edits work fully.
  • You can use Git, so every AI change is a diff you can review and undo.
  • Studio receives the files through the Rojo plugin.

Setup in short: install Rojo, run rojo init, open the folder in Cursor, run rojo serve, and connect from the Rojo plugin in Studio.

Use both

The strongest setup combines them:

  • Rojo + Git for code: reviewable, undoable, searchable.
  • MCP for everything that isn't a file: parts, models, UI layouts, lighting, playtesting and reading the console.

So Cursor edits src/server/Shop.luau as a file, then uses MCP to start a playtest and read the output to check the change. More on the trade-offs in MCP vs Rojo.

Tips

  • Give it Roblox context. A project rules file describing your folder layout and networking rules saves a lot of wrong guesses.
  • Save first. Agents change your place directly through MCP.
  • Several Studio windows? Tools take a studio_id. Ask the agent to run list_roblox_studios first.
  • Not connecting? See MCP not connecting.

Models alongside code

Cursor handles code and Studio edits. For 3D models in your own style, generate them separately and import them. Vi3W turns prompts, photos or sketches into textured, retopologised meshes exported as GLB, FBX or OBJ. Make models in Vi3W.

Last reviewed