Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Roblox Executor MCP Server

No user-submitted related servers found.

    Related Servers

    • Roblox Client MCP

      LiteEagle262
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    • Roblox Executor MCP Server

      jipanjiji
      A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      21
      79 npm
      MIT

    • Roblox Executor MCP

      thegrateminecra-backups
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Lets 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.
      -

    • Roblox Executor MCP Server

      amyyzing
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      79 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 291 tools

    Disambiguation2/5

    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.

    Naming Consistency2/5

    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.

    Tool Count1/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources