Roblox Studio MCP Gateway
Related Servers
Alternatives to Roblox Studio MCP Gateway
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI tools to read the Roblox Studio game tree, edit scripts, insert models, and run playtests via the Studio MCP interface.37 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to drive a running Roblox Studio in real time over a single WebSocket, executing whole Luau programs, installing in-engine controllers, hot-patching scripts during live playtests, and receiving errors, assertions and other events as pushes. It also reaches Roblox Open Cloud for the open place and answers visual questions via a vision sidecar, exposing all of this through nine MCP tools.92MIT
- AlicenseBqualityCmaintenanceEnables a bot to inspect, query, create, edit, and script Roblox Studio instances in token-cheap batches, plus run Luau, playtests, screenshots, and inputs through Roblox's official Studio MCP connection. It runs locally over stdio or an authenticated local HTTP endpoint, returning small structured answers instead of dumping whole games into context.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables Roblox Studio workflow automation beyond the built-in MCP, including opening places, managing assets via Open Cloud, safe Luau execution, and extracting place contents.68 npm1MIT
- AlicenseBqualityCmaintenanceEnables AI agents to control Roblox Studio by launching/closing it, opening places, executing Luau, building scenes, scripts, and GUI, inserting Toolbox assets, and running Play Solo/Run playtests. It also supports scene inspection, property editing, output reading, and undo/redo of agent actions.5030 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to explore, edit, and automate Roblox Studio sessions locally, including browsing instance hierarchies, reading and modifying scripts, manipulating properties, creating instances, building terrain, and running playtests.1,057 npmMIT
TDQS
Scored across 33 tools
Most tools have clearly distinct domains: import/export, scripts, playtest, profiling, input, docs, and device simulation are easy to tell apart. There is some overlap among roblox_search/roblox_grep, roblox_read/roblox_script_get/roblox_attrs, and the multiple script-editing tools, but descriptions provide enough distinction.
All tools share a consistent roblox_ snake_case prefix, which makes the set predictable. However, names mix verb-first patterns (roblox_search, roblox_edit) with noun-only labels (roblox_tree, roblox_attrs, roblox_class, roblox_device), so the convention is not fully uniform.
Thirty-three tools is heavy for a single MCP server and exceeds typical well-scoped ranges. The broad Studio gateway domain justifies many capabilities, but several script-edit and utility tools could likely be consolidated.
The surface covers an unusually broad Studio workflow: scripts, playtests, profiling, backups, import/export, docs, input simulation, multiplayer, network, and device simulation. Minor gaps remain, such as explicit instance creation/deletion and asset upload workflows, but most agent workflows are supported.