Can Claude Code work with Roblox Studio?

Yes. Studio's built-in MCP provides direct access; Baseplate is optional. Its Guide adds a project workflow, local Map and Verify reads, and review of changes and evidence.

Do I need an Anthropic API key?

Use the Claude Code access supplied by your own provider account. Baseplate does not include an AI plan or remove its limits. A free local Map or Verify read needs neither AI access nor an Open Cloud key.

Why is there no Developer tab in Claude?

Claude Desktop and Claude Code have different setup paths. Current Desktop settings group local MCP connections under the Desktop app section and its Extensions manager; older versions used Developer. This guide's Baseplate workflow uses Claude Code CLI.

Do I still need Rojo?

Rojo is optional for Baseplate's Studio-import path. An import is a script snapshot, not automatic synchronization. For a Rojo project, connect its server and plugin to the right place, then check the changed source actually reached Studio.

Can one Claude connection use several Roblox experiences?

The official MCP can list multiple Studio instances. Confirm the game and target its studio_id before edits; local places may lack a place ID.

Setup guide

How to use Claude Code with Roblox Studio

Bring one game, give your agent one clear change, then repeat the same player action in Studio. Start with the connection you need and keep the result small enough to inspect.

Choose your route: the official Studio MCP connects an AI client directly. Baseplate is an optional desktop workspace: its Guide brings project setup, local script maps and scans, agent work and result review into one place.

For the guided Baseplate workflow

Claude Code CLI, installed and signed in on the computer running Baseplate. A Desktop app or browser chat alone is not the CLI. Follow the official Claude Code setup.
A saved copy of your game or its local project folder.
Roblox Studio for gameplay tests. A local scan can be your first result without a live connection.

1. Choose the game you want to improve

Open Guide → Fix a bug, then Choose my game. Select your local project, or choose the Studio import path after saving a separate copy. The Guide walks you through selecting the game and confirming the import.

An import is a script snapshot. Editing it is not automatic Rojo sync. For a Rojo project, start its server and connect Studio's Rojo plugin to that project. Check the actual source in Studio before testing either workflow.

2. Give Claude one observable target

In What should change for the player?, describe what happens, what should happen and the steps to repeat. “After checkpoint 3, touching checkpoint 1 and resetting sends me backwards” is a clearer task than “fix my game”. Use a problem from your own project and ask for a focused change.

3. Connect the tools for this change

Expand Connect the tools for this change. Select Claude Code under AI for building and playtesting, then use Check AI setup. After installing a CLI, fully restart Baseplate so it can find the installation.

Open How do I connect Studio? and follow the detected next step for the Baseplate Bridge and Studio MCP. Restart Studio after a plugin installation and approve its HTTP request when prompted. Use Check setup; an installed file is not proof of a live connection. Provider account restrictions or a Studio connection error still need resolution before a runtime test.

4. Review the change and repeat your test

When Guide says Ready for one useful improvement, choose Build & test this change. Watch the agent's requests and review its edits. Confirm the changed source reached the selected game, then repeat the original player action yourself.

A useful result: the right game, reviewed changes, the same test before and after, and an observed outcome. A clean console alone does not prove the mechanic works. A recorded PASS covers its executed checks, not the whole game.

No Developer tab in Claude Desktop?

This guide's workflow uses Claude Code CLI. If you are following a Desktop tutorial, its settings may look different: the current route is Settings → Desktop app, then Manage beside Extensions. Local MCP connections are in that area; older layouts used Developer. The current Claude Desktop help documents both layouts.

That menu belongs to Claude Desktop. Its setup is separate from the Claude Code CLI workflow above.

Using more than one open game?

Ask the connected agent to list Studio instances and confirm the game before making changes. It targets an instance ID; one configuration is not tied permanently to one experience. See Roblox's multi-instance instructions.

List the connected Studio windows. Do not change anything.
Show their names and place IDs where available.
Ask me to confirm the game before editing.

Start without connecting AI

In Guide, choose Find what to improve, select your project and use Open free local scan. Verify highlights risks and missing evidence. This scan needs neither an AI account nor an Open Cloud key; its findings still need review and testing.

Honest limits

AI access is separate. Use your own supported Claude account. Baseplate does not remove provider limits or organization restrictions.
Configured is not tested. Runtime proof needs an actual connected Studio session and an executed test. Static findings are a different result.
Use the current project connection. Baseplate prepares MCP settings for its launched session. Copying a fixed localhost address from another setup can select the wrong port or workspace. Use the separate Codex and Cursor instructions for those clients.
Review before publishing. One fixed runtime error is not a security audit. The RemoteEvent checklist provides a separate review path.

Bring one game. Get one useful result.

Start with a free local scan or the core one-agent workflow. Use the AI access you already have.

Download Baseplate free

Stuck on your own project? Ask for free written help →