Skip to main content
Glama
jipanjiji

Roblox Executor MCP Server

by jipanjiji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Roblox Executor MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      139 npm
      MIT

    • Roblox Executor MCP Server

      virtualtable
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with a running Roblox game client, including executing Lua code, inspecting scripts, searching instances, intercepting remote events via Sigma Spy, and controlling the GUI.
      139 npm
      1
      MIT

    • 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 MCP Server

      33jrdd
      F
      license
      B
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with running Roblox game instances by inspecting the game hierarchy, reading client-side scripts, and executing Lua code directly within the Roblox client through a WebSocket bridge.
      4
      30 npm
      -
    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

    A3.8/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools target clearly distinct actions and resources, with helpful cross-references in descriptions (e.g. script-grep vs semantic-search-scripts, execute vs get-data-by-code). The main friction points are the three execution tools (execute, execute-file, get-data-by-code) and the subtle block-remote vs ignore-remote distinction, though descriptions mitigate these.

    Naming Consistency4/5

    Naming is largely consistent, using kebab-case with verb_noun ordering (list-clients, get-game-info, block-remote, click-button). Minor deviations exist where noun precedes verb (script-grep, screenshot-window) and single-verb names (execute), but overall it reads predictably.

    Tool Count4/5

    21 tools is on the heavier side but justified by the broad domain spanning client routing, Luau execution, instance/script exploration, remote-spy control, and UI automation. Each tool earns a distinct place, with only light overlap in the execution group.

    Completeness4/5

    Coverage is strong across execution, introspection (instances, scripts, descendants), remote-spy lifecycle (ensure/get/clear/block/ignore), UI interaction, and screenshots. Minor gaps like element-based screenshotting or text reading are absent but not critical to core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources