roblox-studio
Related Servers
Alternatives to roblox-studio
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to execute Lua code, inspect scripts, spy on remotes, and interact with a running Roblox game client through an MCP interface.162266 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA production MCP integration that lets AI agents control Roblox Studio to autonomously build, test, and debug Roblox games. Provides 39 tools for explorer control, script management, terrain generation, and autonomous testing.3MIT
- 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.66 npm7MIT
- AlicenseNot gradedqualityBmaintenanceConnects ChatGPT to Roblox Studio's built-in MCP, enabling natural-language reading and writing of game data, including executing Luau code and modifying scripts and instances.MIT
- AlicenseNot gradedqualityCmaintenanceBridges coding agents with Roblox Studio, enabling inspection, generation, editing, and validation of Roblox places through natural language.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI IDEs and agents to connect to and control Roblox Studio through the Model Context Protocol, bridging to Studio's native StudioMCP daemon to interact with the active place and DataModel.46 PyPIMIT
TDQS
Scored across 25 tools
Most tools target distinct resources or actions, but several map-lifecycle tools overlap (apply_scene_spec vs create_blockout, validate vs readiness_check) and batch instance operations partially duplicate single-instance create/set/delete. Descriptions mostly clarify the boundaries, so misselection risk is moderate rather than severe.
All tool names use snake_case with consistent studio_/map_/terrain_ prefixes, making the convention easy to follow. Minor deviations exist: map_readiness_check is a noun phrase while neighboring map tools use verb_noun, and studio_ping/visual_probe are less action-specific.
25 tools is at the heavy end of the acceptable range, spanning instance CRUD, camera control, map lifecycle, testing, terrain, export, and diagnostics. Each maps to a plausible operation, but the breadth makes the surface feel borderline rather than tightly scoped.
The set covers full instance CRUD plus batch patching, camera/viewport inspection, playtest/test execution, map generation/validation, export, terrain, and diagnostics. Gaps are minor—no obvious place save/publish or instance duplication workflow—but agents could work around via execute_luau.