Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_PLUGINS_DIRNoDirectory where the gateway checks for MCPPlugin.rbxmx. Set this to the active plugins folder when using another Studio installation or Wine prefix.Vinegar's default Studio plugins directory
ROBLOX_BRIDGE_URLNoHTTP address of the upstream bridge.http://127.0.0.1:58741
ROBLOX_BRIDGE_TOKEN_FILENoPath to the bridge token file.~/.robloxstudio-mcp/auth-token

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Roblox Studio autonomous gateway — Explorer, Scripts, Toolbox, playtest, verify

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
roblox_statusC

Bridge + plugin status and effective env config.

roblox_ensure_readyC

Plugin + bridge readiness (never launches processes).

roblox_planC

Deterministic ordered step list for an edit intent.

roblox_searchC

Search instances in the open Studio place.

roblox_readB

Read properties of one instance by path.

roblox_editB

Set instance properties. Dry-run by default; back up first for real edits.

roblox_execC

Execute Luau in edit/server/client domain.

roblox_buildC

Generate a model from a text prompt via the bridge.

roblox_toolboxC

Toolbox gateway: insert ids, preview one asset, or search by query.

roblox_playtestC

Screenshot + runtime logs, then verify verdict.

roblox_profileC

Flag profiler readings over budget.

roblox_backupB

Save current project structure to a dated JSON file.

roblox_script_getC

Get script source, optionally a line range.

roblox_script_setC

Set script source. Dry-run by default.

roblox_script_editC

Replace first occurrence of old_string in a script.

roblox_script_linesC

Insert (after start_line) or delete (start_line..end_line) script lines.

roblox_grepC

Grep script sources across the place.

roblox_replaceB

Find and replace across scripts. Dry-run by default.

roblox_placeC

Place info: id, name, data model.

roblox_treeC

Project structure / file tree.

roblox_attrsC

Get instance attributes.

roblox_selectionB

Get selection, or set it when paths are given.

roblox_classC

Class info: properties and events.

roblox_exportC

Export instance to .rbxm file (0600).

roblox_importC

Import .rbxm file (max 37.5MB).

roblox_captureD

scene | memory | script-profiler | micro-profiler.

roblox_soloC

Start/stop solo playtest: mode play|stop.

roblox_multiplayerC

Multiplayer playtest: start|add|leave|end|state.

roblox_breakpointsC

List/set/clear script breakpoints.

roblox_inputC

Simulate mouse/keyboard input in Studio.

roblox_docsC

Roblox engine reference docs (public, no Studio needed).

roblox_networkC

Set playtest network profile via Luau.

roblox_deviceD

Device simulator state/set.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.7/5.0

Scored across 33 tools

Disambiguation4/5

Most tools have clearly distinct domains: import/export, scripts, playtest, profiling, input, docs, and device simulation are easy to tell apart. There is some overlap among roblox_search/roblox_grep, roblox_read/roblox_script_get/roblox_attrs, and the multiple script-editing tools, but descriptions provide enough distinction.

Naming Consistency4/5

All tools share a consistent roblox_ snake_case prefix, which makes the set predictable. However, names mix verb-first patterns (roblox_search, roblox_edit) with noun-only labels (roblox_tree, roblox_attrs, roblox_class, roblox_device), so the convention is not fully uniform.

Tool Count3/5

Thirty-three tools is heavy for a single MCP server and exceeds typical well-scoped ranges. The broad Studio gateway domain justifies many capabilities, but several script-edit and utility tools could likely be consolidated.

Completeness4/5

The surface covers an unusually broad Studio workflow: scripts, playtests, profiling, backups, import/export, docs, input simulation, multiplayer, network, and device simulation. Minor gaps remain, such as explicit instance creation/deletion and asset upload workflows, but most agent workflows are supported.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues