Roblox Super 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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_projectA | (RECOMMENDED ENTRY POINT) Rebuilds the versioned project index from live Studio evidence and safely retains the last valid cache on failure. |
| get_project_snapshotC | Returns a bounded project overview with place identity, counts, remotes, modules, cache provenance, and paginated indexed instances. |
| inspect_instanceA | Batch-inspects exact Studio paths, returning properties, attributes, tags, children, and optional bounded script source. |
| find_systemA | (RECOMMENDED) Ranked system discovery with match evidence across paths, functions, attributes, dependencies, services, and remotes. |
| search_sourceA | Searches live Luau source by literal text, Luau pattern, exact symbol frontier, or method call with line-numbered snippets. |
| read_script_contextA | Reads a line-numbered live source window plus dependencies, dependents, remotes, functions, attributes, and source hash. |
| get_related_codeC | Ranks indexed files for a task with field-level match evidence, relationships, services, and remote participation. |
| impact_analysisA | (RECOMMENDED BEFORE EDITING) Calculates change risk from direct/transitive dependents, persistence, remotes, shared state, and ambiguity. |
| find_dependenciesB | Returns direct/transitive dependency and dependent graphs with cycles, unresolved requirements, ambiguity, and service usage. |
| trace_data_flowA | Traces observed remote and persistence participants for a state name while clearly separating observation from inferred flow. |
| get_remote_registryB | Lists remotes, callers/listeners, execution sides, methods, missing peers, naming findings, and evidence coverage. |
| validate_remote_contractA | Audits remote contracts for runtime validation, rate limiting, server authority, naming, missing peers, and client-supplied numbers. |
| sanity_check_scriptC | Performs a line-aware Luau audit for strict typing, lifecycle, remote validation, persistence safety, forbidden APIs, and modern standards. |
| audit_lifecycleA | Audits live scripts for unowned connections, uncancellable threads, unbounded yields, stale references, and missing cleanup. |
| audit_performanceA | Audits live hot paths for per-frame allocation, cloning, hierarchy scans, raycast pressure, polling, and missing pre-allocation. |
| audit_data_integrityB | Audits ProfileStore/ProfileService/DataStore and receipt flows for session, pcall, persistence, yield, and grant-order safety. |
| detect_race_conditionsB | Finds read-yield-use hazards, re-entrant handlers, concurrent state writes, and competing anchor authorities. |
| find_dead_codeA | Returns confidence-scored unused module, function, remote, and attribute candidates without authorizing deletion. |
| generate_change_planA | Produces a non-mutating, evidence-backed implementation and verification plan for a requested feature or change. |
| apply_script_patchB | Atomically applies exact-text script edits with source-hash and match-count preconditions, dry-run, idempotency, verification, and rollback. |
| create_architectureA | Idempotently creates or updates folders, scripts, remotes, attributes, tags, and scalar/typed properties; created instances retain a transaction marker for safe rollback identity. |
| verify_changeA | Verifies a recorded transaction against live Studio state, reruns source sanity audits, and reports index drift. |
| rollback_changeA | Reverts a recorded transaction in reverse order with drift preconditions and optional dry-run. |
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 23 tools
Most tools have distinct purposes, but find_system and get_related_code both rank files by match evidence across similar dimensions, which could cause confusion. The audit_* tools are differentiated by their target concern, so overall boundaries are mostly clear.
All tool names follow a consistent snake_case verb_noun pattern (e.g., analyze_project, get_project_snapshot, audit_lifecycle), making the set highly predictable and easy to navigate. There are no mixed conventions or vague names.
At 23 tools, the server is in the borderline heavy range, and the presence of near-duplicate tools like find_system and get_related_code suggests it could be slightly consolidated. The breadth of Roblox development is large, but the count feels marginally bloated rather than well-scoped.
The tool surface covers analysis, auditing, modification, verification, and rollback comprehensively for Roblox code. However, it lacks explicit instance deletion or standalone script creation (only via create_architecture), which are minor gaps agents could work around.