Roblox-MCP
Related Servers
Alternatives to Roblox-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for controlling and reverse engineering Roblox games, providing 132 tools across 8 categories for instance exploration, property inspection, input simulation, and more.125 npm6MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI agents to execute Lua code, inspect scripts, spy on remotes, and interact with running Roblox game clients, including support for mobile executors on Android and iOS.100 npm1MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that enables AI agents to interact with a running Roblox game client, including code execution, script inspection, remote spying, and GUI automation.100 npm7MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that allows AI agents to execute code, inspect scripts, spy on remotes, and interact with a running Roblox game client.100 npm15MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI agents drive a running Roblox client, execute Luau, decompile scripts, spy on remotes, and automate UI, with a bundled Vyre dashboard for live monitoring.100 npmMIT
- FlicenseNot gradedqualityCmaintenanceProvides Roblox game inspection and manipulation capabilities through MCP, including exploring the instance hierarchy, editing properties, decompiling scripts, and interacting with remote events.-
TDQS
Scored across 26 tools
Most tools have clearly distinct purposes and the descriptions cross-reference alternatives (e.g. execute vs get-data-by-code, script-grep vs semantic-search-scripts). A few boundaries are fuzzy: execute/execute-file/get-data-by-code all run Luau with differing output behavior, and ignore-remote vs block-remote both act on remotes, though descriptions do clarify the distinction.
Nearly all tools follow a consistent kebab-case verb_noun pattern (get-script-content, set-active-client, clear-remote-spy-logs, fire-remote). Minor deviations exist in noun-first names like script-grep and semantic-search-scripts, but the overall convention is readable and predictable.
At 26 tools this sits at the upper edge of the ideal range, but the domain is unusually broad (client routing, code execution, player control, script decompilation/search, instance introspection, remote spy, GUI automation, screenshots), so most tools earn their place rather than being redundant.
The surface covers the full exploitation lifecycle: client discovery/routing, execution, player manipulation, script reading and both grep/semantic search, instance and game introspection, remote spying/firing/blocking, GUI interaction, and OS-level screenshots. No obvious dead ends for the stated purpose.