Roblox Studio MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROBLOX_MCP_PORT | No | HTTP bridge port | 28821 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| roblox_getA | Read-only queries against the Roblox Studio scene. Use the "action" parameter to select what to retrieve. Actions:
|
| roblox_manageA | Mutate instances in the Roblox Studio scene. Actions:
Property format: vectors as {X,Y,Z}, colors as {R,G,B} (0-1 range), booleans, strings, numbers. Example: {"Position": {"X":0,"Y":5,"Z":0}, "Size": {"X":4,"Y":1,"Z":4}, "Anchored": true, "Material": "Neon", "Color": {"R":1,"G":0,"B":0}} |
| roblox_scriptA | Create, read, update, and execute Lua scripts in Roblox Studio. Actions:
Common parent locations: "ServerScriptService" (server scripts), "StarterPlayerScripts" (local scripts), "ReplicatedStorage" (modules). |
| roblox_sceneA | Control the camera and capture rendered viewport screenshots. Actions:
Typical workflow: move_camera (frame your subject) → screenshot (see the result) → evaluate → adjust. |
| roblox_toolboxA | Search the Roblox Creator Store, insert models, and sanitize them. Actions:
|
| roblox_playtestA | Control Roblox Studio playtest sessions and interact with the running game. Actions:
Workflow: start → interact/observe → screenshot (via roblox_scene) → evaluate → stop → fix → repeat. |
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 6 tools
Each tool has a clearly distinct purpose: roblox_get for read-only queries, roblox_manage for mutations, roblox_playtest for session control, roblox_scene for camera/screenshot, roblox_script for script handling, and roblox_toolbox for asset management. The actions within each tool are well-defined and non-overlapping, making tool selection straightforward for an agent.
All tool names follow a consistent 'roblox_' prefix with a descriptive suffix (e.g., get, manage, playtest, scene, script, toolbox). This pattern is uniform across all six tools, making them easily identifiable and predictable within the server's domain.
With 6 tools, the server is well-scoped for Roblox Studio automation, covering scene inspection, manipulation, playtesting, visualization, scripting, and asset management. Each tool serves a distinct and necessary function, with no redundancy or missing core areas, making the count ideal for the domain.
The tool set provides comprehensive coverage for Roblox Studio workflows, including CRUD operations (e.g., create, update, delete), scene analysis, playtesting, camera control, script management, and asset handling. There are no obvious gaps; agents can perform end-to-end tasks from asset insertion to scene evaluation and debugging.