How to use Cursor with Roblox Studio

Connect Cursor directly to Studio

Roblox Studio has a built-in MCP server. Baseplate and its Bridge are not required for this direct route. Use an up-to-date Studio and an installed Cursor client.

1. Open a saved copy of your game in Studio.
2. In Assistant → … → Manage MCP Servers, turn on Enable Studio as MCP server.
3. Expand Quick connect and select Cursor. If it is missing, check the client installation and restart Studio.
4. Restart the client after configuration, then ask it to list the connected Studio windows. Confirm the right game before allowing edits.

Check the connection indicator in Studio. For manual configuration or more than one open game, use Roblox's current MCP instructions. The agent must target the correct studio_id; an open window alone does not select the right game.

Cursor editor or Cursor CLI?

Cursor's editor can use the direct route above. Inside Baseplate, install Cursor Agent CLI separately and sign in on the same computer. The editor alone does not complete that CLI setup. Follow Cursor's installation instructions for your system, including native Windows. Your own account access and usage limits apply; Baseplate Pro does not include a Cursor plan.

Use Cursor inside Baseplate

Baseplate brings the project, local script map and scan, agent work and result review into one desktop workspace. Start with one change:

1. Guide → Fix a bug → Choose my game. Select the local project or follow the Studio import steps on a saved copy.
2. In What should change for the player?, state the symptom, expected behaviour and a repeatable test. For example: “After checkpoint 3, touching checkpoint 1 and resetting sends me backwards.”
3. Expand Connect the tools for this change. Choose Cursor under AI for building and playtesting, then use Check AI setup. Fully restart Baseplate after installing the CLI.
4. Follow How do I connect Studio? for the Baseplate Bridge and Studio MCP. Use Check setup. When Guide says Ready for one useful improvement, choose Build & test this change.

Review the agent's requests and edits, check the changed source in the selected Studio game, then repeat your original test. A Studio import is a script snapshot, not automatic sync. For a Rojo project, start its server and connect the Rojo plugin to that project before testing.

Get a first result without AI

Open Guide → Find what to improve, select your local project and choose Open free local scan. Verify highlights script risks and missing evidence. No AI account or Open Cloud key is needed for this read. Open one finding, inspect its file and line, then choose what to check next.

Cursor cannot see the Studio tools?

• CLI missing or signed out: complete the provider setup, restart Baseplate and run Check AI setup again. An editor login is not proof the CLI is ready.
• No Studio connection: check the enabled server and connected-client indicator. In Baseplate, follow Check setup for the detected next step; an installed Bridge file is not a live connection.
• Wrong project: confirm both the local workspace and selected Studio game. Open the Git root as the Baseplate workspace when your scripts belong to a Git project.
• Tools described but not called: inspect the server's connection, approval and available tools before asking the model to retry. That symptom alone does not identify the cause.

Where do Cursor's MCP settings live?

Cursor uses project .cursor/mcp.json or global ~/.cursor/mcp.json. For manual CLI checks, agent mcp list shows the configuration source and state; agent mcp list-tools <identifier> lists tools. Review which server you are enabling. See Cursor's CLI MCP help and configuration reference.

Use the current project connection prepared by Baseplate. A copied localhost port or workspace path from someone else's setup may point at the wrong session.

Does Baseplate overwrite my Cursor settings?

Baseplate preserves unrelated entries in project .cursor/mcp.json and does not rewrite global Cursor configuration. It manages baseplate and, during explicit Studio setup, Roblox_Studio. Malformed existing files are refused instead of overwritten.