Roblox Executor MCP Server
Related Servers
Alternatives to Roblox Executor MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to inspect and control a live Roblox client through an executor, including reading console output, exploring the instance tree, decompiling scripts, monitoring remote traffic, and running Luau code.MIT
- AlicenseAqualityDmaintenanceEnables AI agents to connect to one or more running Roblox game clients to execute Lua code, decompile and search scripts, browse instances with CSS-like selectors, intercept and block remotes, drive GUIs, and capture screenshots through a local dashboard and bridge.2157 npmMIT
- -licenseNot gradedqualityNot gradedmaintenanceLets AI agents interact with a live Roblox game via an executor, supporting multi-agent sessions and tools for executing Lua, decompiling scripts, exploring game instances, and capturing screenshots.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with a running Roblox game client, including executing Lua code, inspecting scripts, and spying on remotes, with a local dashboard for monitoring and control.57 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with a running Roblox game client to execute Lua code, inspect scripts, spy on remotes, and more.57 npm216MIT
- AlicenseNot gradedqualityAmaintenanceConnects AI assistants to a live Roblox executor session to read console logs and errors, search and inspect the instance tree, read scripts, change properties, and run Lua, while reporting connection status on every call.4MIT
TDQS
Scored across 291 tools
With 291 tools, many overlap heavily: list-strings/find-string-xrefs/find-constants-xref/find-functions-by-constant all search closure constants; remote-spy/monitor-remote/trace-remote-traffic/ensure-remote-spy/get-remote-spy-logs/configure-remote-spy all manage remote capture; hook-function/block-function/spoof-function-return/hook-and-log-function/count-function-calls/trace-call-durations all install function hooks; find-hidden-instances/find-detached-instances/get-nil-instances/find-hidden-remotes/find-hidden-scripts/find-running-scripts heavily overlap. Descriptions are detailed but the boundaries between these clusters are blurry, causing misselection.
Conventions are mixed: many kebab-case verb_noun tools (find-string-xrefs, list-gc-tables, get-instance-properties), but also camelCase (search-instances, get-players, select-client), terse single-word tools (execute, script, run-luau, draw-create, ws-list, filter-gc), and others with irregular verbs. The pattern is not predictable across the set.
291 tools is an extreme mismatch for any coherent server surface; many clusters duplicate functionality (multiple hidden-instance finders, multiple spy managers, multiple hooking variants), indicating over-expansion rather than well-scoped coverage. This is far beyond the 15-tool well-scoped range and well past the 25+ 'too many' threshold.
For the Roblox executor domain the surface is remarkably exhaustive: reflection/GC scanning, closure inspection, hooking, remote/signal monitoring, GUI driving, file I/O, crypto, drawing, packet, WebSocket, and agent-orchestration tools are all present. Minor lifecycle gaps (e.g. no first-class 'list all active hooks/spies' consolidated view) are workarounds, not dead ends.