MCP orchestration is how the Roblox Game Skill drives Roblox Studio directly — creating instances, writing scripts, running playtests, reading console output, and fixing errors — without the developer ever leaving their editor. Rather than generating code for you to paste, Claude calls MCP tools in planned sequences: scaffolding the DataModel, generating server and client scripts, wiring RemoteEvents, inserting Creator Store assets, running a playtest, reading errors, and iterating until the build is clean. This document describes how that orchestration works: which server Claude detects, which tools it selects for each task, how autonomous build sequences are structured, and how errors are handled.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/brockmartin/roblox-game-skill/llms.txt
Use this file to discover all available pages before exploring further.
Mode Detection
On every session start — or whenever Studio interaction is first requested — Claude probes the available tool names to determine which MCP server is connected and which operating mode to enter.Probe for Community Server tools
Look for characteristic tool names from the community server (
boshyxd/robloxstudio-mcp):
execute_luau, get_file_tree, grep_scripts, create_build, search_objects, get_instance_properties, get_script_sourceIf any of these are present → enter Full Mode (39 tools available).Probe for Official Server tools
If community tools are absent, look for tools from the official server (
Roblox/studio-rust-mcp-server):
run_code, insert_model, get_console_output, start_stop_play, run_script_in_play_mode, get_studio_modeIf these are present but community tools are not → enter Standard Mode (6 tools).Detection Priority
If both servers are detected simultaneously, prefer the Community Server for its broader toolset (39 tools vs. 6). Fall back to individual Official Server tools only when a community equivalent is unavailable or failing.
Mode Capabilities at a Glance
Full Mode
Community Server — 39 toolsExploration, building, testing, asset management, bulk operations, history. Full autonomous build cycles without manual steps.
Standard Mode
Official Server — 6 tools
run_code, insert_model, get_console_output, start_stop_play, run_script_in_play_mode, get_studio_mode. Capable but requires workarounds for exploration tasks.Offline Mode
No MCP — 0 toolsClaude generates annotated copy-paste code blocks, directory structures, and setup checklists for manual execution.
Tool Selection Heuristics
Claude selects tools based on the task at hand, the current Studio mode, and which server is connected.Full Mode Tool Selection
| Task | Primary Tool | Notes |
|---|---|---|
| Understand project layout | get_file_tree → get_project_structure | Always the first step in any project exploration |
| Find a specific instance | search_objects | Filter by name or class |
| Read a script’s source | get_script_source | Before editing; never overwrite blindly |
| Find all references to a symbol | grep_scripts | Searches across all scripts by pattern |
| Create or modify instances | execute_luau | Primary workhorse — create folders, scripts, parts |
| Scaffold complex structures | create_build | Rooms, maps, hierarchical instance trees |
| Insert a Creator Store asset | Creator Store search → insert | Search first; confirm before inserting |
| Validate changes at runtime | start_playtest → get_playtest_output → stop_playtest | Always in this order |
| Roll back a change | undo | Before and after bulk changes |
| Audit many instances at once | mass_get_property | Read before bulk write |
Standard Mode Adaptations
Standard Mode lacks all exploration tools. Compensate withrun_code + get_console_output:
Offline Mode Output Format
When no MCP server is connected, every script block gets a placement header:default.project.json mapping included.
Pre-Operation Checks
Before any build or modification sequence, Claude verifies Studio state:Check Studio mode
Call
get_studio_mode (Standard Mode) or infer from context (Full Mode). Never execute build code while a playtest is active — changes to the DataModel during play mode are discarded when the session ends.Read before write
Always inspect a script’s current source with
get_script_source before overwriting. Log the previous content or at least its key function names.Autonomous Build Sequence
A complete build cycle from a feature specification to a working, error-free game system. This sequence is what Claude executes in Full Mode when asked to scaffold a new game or add a major system.Scaffold — Understand and Plan
Generate Core Systems
For each system (combat, inventory, UI, etc.):
- Generate the server script →
execute_luauto create and populate aScriptinstance - Generate the client script →
execute_luauto create and populate aLocalScript - Generate shared modules →
execute_luauto create and populateModuleScriptinstances
RemoteEvent and RemoteFunction instances between client and server:Insert Assets
Search the Creator Store for needed models, audio, or meshes:Position and configure inserted assets via
execute_luau after insertion.Debug Loop Pattern
Systematic error resolution used during testing and when fixing issues reported by the user.Error Pattern Recognition
After readingget_playtest_output, scan for these high-priority patterns:
| Pattern | Meaning |
|---|---|
"attempt to index nil" | A variable is nil where an object was expected — missing require or WaitForChild |
"Infinite yield possible" | WaitForChild didn’t find its target — wrong path or load-order issue |
"is not a valid member" | Property or child name is wrong — typo or renamed API |
"HTTP 429" | DataStore throttling — too many requests |
"Script timeout" | Infinite loop or blocking operation on the main thread |
"attempt to call a nil value" | Calling a function that doesn’t exist — bad require or wrong method name |
Bulk Modification Pattern
Safe large-scale changes across many instances.Plan and checkpoint
Review the affected instance count and sample values. Then create an undo waypoint:
Project Exploration Pattern
Understanding an unfamiliar place file before making any changes.Safety Guidelines
| Scenario | Rule |
|---|---|
| Studio is in Play mode | Stop the playtest before modifying the DataModel |
| Bulk delete | Create undo waypoint first; confirm with user for named/significant instances |
| Script overwrite | Read current source with get_script_source before replacing |
| Experimental change | Create undo waypoint; use undo if the result is wrong |
| Running code in play mode | Use run_script_in_play_mode (Official); use get_playtest_output for results |
Common Anti-Patterns
Running code without checking Studio state
Running code without checking Studio state
Wrong:Right:
Bulk changes without undo waypoints
Bulk changes without undo waypoints
Wrong:Right:
Assuming tool availability
Assuming tool availability
Wrong:Right:
Blind script overwrites
Blind script overwrites
Wrong:Right:
Ignoring error output after execute_luau
Ignoring error output after execute_luau
Wrong:Right: