Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RBXMCP_DEVNoSet to '1' to enable the dev HTTP route for direct Lua execution. Used for managed/corporate environments where MCP tools are blocked.0

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
execute_luaA

Run a Luau code string inside Roblox Studio (via loadstring) and return its captured output, return values, and any error with traceback. Use this to build, script, inspect, or modify anything in Studio; iterate by reading the error and re-running.

read_studio_stateA

Inspect Studio state in a clean form: 'selection' (current selection), 'explorer_tree' (workspace tree to a depth), 'instance' (one instance by dotted path, e.g. 'Workspace.Model.Part'), or 'services_summary'. Runs a server-owned snippet — no arbitrary code.

get_errorsA

Return the most recent failed executions (message + traceback). Useful for recovering context.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: execute_lua runs arbitrary code, read_studio_state provides structured read-only inspection, and get_errors surfaces recent failures. No overlap or ambiguity.

Naming Consistency5/5

All three tool names follow the same verb_noun pattern in snake_case (execute_lua, read_studio_state, get_errors). The naming is uniform and predictable.

Tool Count5/5

Three tools is well-scoped for this server. execute_lua acts as a powerful general-purpose action tool, while the other two provide safe inspection and error recovery, so no extra tools are needed.

Completeness5/5

execute_lua can perform any build, script, or modification task within Roblox Studio, read_studio_state covers structured inspection needs, and get_errors closes the debugging loop. The set covers the full workflow without dead ends.

Maintenance

ActivitySlowing
ResponsivenessNo issues