roblox-studio-bridge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_statusA | List connected Roblox Studio sessions (edit DataModel, play-test server and each play-test client). |
| run_luauA | Execute Luau in a Studio DataModel and return print/warn output plus returned values. Code may yield (task.wait). |
| get_logsB | Read Studio Output (LogService) captured from connected sessions. Use |
| screenshotA | See what Studio shows. Default mode 'window' captures the real Studio window (macOS; briefly brings Studio forward if it is on another Space). Use |
| sync_projectA | Push scripts from a Rojo project file into the open place (edit mode only). Creates/updates scripts and folders, removes previously synced instances that no longer exist on disk. |
| start_testA | Start a Studio test from the edit DataModel. mode: play (solo, default), run (server only), multiplayer (players 1-8 simulated clients). Waits until the server and client sessions connect. |
| stop_testA | End the running Studio test session. |
| add_playersB | Add simulated clients to a running multiplayer test. |
| list_guiA | List the PlayerGui hierarchy of a play-test client with positions, visibility and text. |
| reload_pluginA | Hot-reload the StudioBridge core (plugin/Core.luau) in every connected session. |
| get_treeC | Describe the instance hierarchy under a path such as 'Workspace.Camp' (dot separated from game). |
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 11 tools
Each tool targets a distinct capability: session listing, code execution, logs, screenshots, project sync, test lifecycle, GUI inspection, plugin reload, and tree traversal. Even where run_luau returns print output, get_logs is clearly the historical log reader, so no two tools are easily confused.
Most tools follow a clear verb_noun snake_case pattern such as run_luau, start_test, stop_test, add_players, and get_tree. Minor deviations like studio_status (noun phrase) and screenshot (single word without object) keep it from being perfectly consistent.
Eleven tools is well within the ideal range for a domain-specific server, and each tool covers a meaningful part of the Roblox Studio workflow without redundancy or bloat.
The surface covers session discovery, arbitrary Luau execution, log access, visual inspection, project syncing, test lifecycle management, simulated players, GUI hierarchy listing, and instance tree traversal. run_luau also provides a powerful escape hatch for any specialized operation not explicitly exposed.