roblox-studio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROBLOX_STUDIO_BRIDGE_TOKEN | No | Optional stable token for the Roblox Studio bridge. If not set, a token is generated and printed by the MCP server. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| studio_pingA | Check local Roblox Studio plugin status and return version, place, and connection state. |
| studio_get_treeC | Read a bounded Instance tree from Roblox Studio. |
| studio_find_instancesB | Find Instances by name, className, tag, or path prefix. |
| studio_get_propertiesC | Read serialized properties for a single Instance. |
| studio_create_instanceC | Create an allowed Instance class under a requested parent path. |
| studio_set_propertiesC | Set validated serialized properties on one Instance. |
| studio_delete_instancesC | Delete Instances. Requires confirmToken; intended for generated content. |
| studio_patch_instancesC | Apply a batch of create, set, ensure, and delete operations inside managed generated roots. |
| studio_execute_luauC | Execute Luau in Studio only when explicitly enabled by config. |
| studio_get_cameraA | Read the current Roblox Studio viewport camera state. |
| studio_set_cameraC | Move the Roblox Studio viewport camera to inspect generated content. |
| studio_focus_instanceC | Focus the Studio viewport camera on an Instance from a named direction. |
| studio_visual_probeC | Set the Studio camera and raycast a viewport grid to report visible hit parts. |
| map_apply_scene_specC | Dry-run or apply a SceneSpec map into Workspace/MapDrafts. |
| terrain_generateC | Generate terrain through Roblox Terrain API via the Studio plugin. |
| map_create_blockoutC | Create or dry-run a greybox blockout from a SceneSpec. |
| map_refine_visualsA | Refine generated map visuals without changing gameplay layout. |
| map_validateC | Validate generated map safety and geometry. This is not a final visual readiness check. |
| map_readiness_checkB | Run final visual-readiness contract checks for generated maps after map_validate. |
| studio_read_outputC | Return recent output lines mirrored by the Studio plugin. |
| studio_start_playtestB | Ask Studio plugin to start playtest, or return a manual fallback. |
| studio_stop_playtestB | Ask Studio plugin to stop playtest, or return a manual fallback. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
All tools have clearly distinct purposes. The map tools cover a complete pipeline (blockout, refine, validate, apply, readiness check), studio tools handle instance management, camera, properties, playtest, etc., and terrain is separate. No overlapping functionality.
Tool names follow a consistent pattern of prefix_group_action (e.g., map_create_blockout, studio_find_instances, terrain_generate). All use snake_case and descriptive names, making the set predictable and easy to navigate.
With 22 tools, the set is slightly above the typical well-scoped range (3-15), but given the breadth of Roblox Studio operations (map generation, instance management, camera, playtest, terrain), the count is still reasonable and not excessive.
The tool surface covers the full map generation lifecycle, comprehensive instance CRUD (via create, delete, patch, properties), camera control, playtest, terrain generation, and diagnostic tools. No obvious gaps for typical Studio automation tasks.