Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ROBLOX_STUDIO_BRIDGE_TOKENNoOptional 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
studio_export_modelB

Save a managed build root as a private local binary Roblox model under generated/exports.

studio_capture_viewportB

Capture only the Roblox 3D viewport as a private local PNG without desktop or Studio panels. Never opens a permission prompt.

studio_run_testB

Execute trusted project test code in Studio Run or Play mode with timeout cleanup. Requires RUN_STUDIO_TEST confirmation. Not a sandbox. The managed ModuleScript must return a function.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 25 tools

Disambiguation4/5

Most tools target distinct resources or actions, but several map-lifecycle tools overlap (apply_scene_spec vs create_blockout, validate vs readiness_check) and batch instance operations partially duplicate single-instance create/set/delete. Descriptions mostly clarify the boundaries, so misselection risk is moderate rather than severe.

Naming Consistency4/5

All tool names use snake_case with consistent studio_/map_/terrain_ prefixes, making the convention easy to follow. Minor deviations exist: map_readiness_check is a noun phrase while neighboring map tools use verb_noun, and studio_ping/visual_probe are less action-specific.

Tool Count3/5

25 tools is at the heavy end of the acceptable range, spanning instance CRUD, camera control, map lifecycle, testing, terrain, export, and diagnostics. Each maps to a plausible operation, but the breadth makes the surface feel borderline rather than tightly scoped.

Completeness4/5

The set covers full instance CRUD plus batch patching, camera/viewport inspection, playtest/test execution, map generation/validation, export, terrain, and diagnostics. Gaps are minor—no obvious place save/publish or instance duplication workflow—but agents could work around via execute_luau.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues