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.622761MIT
- AlicenseNot gradedqualityBmaintenanceA 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.1MIT
- 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.767MIT
- AlicenseNot gradedqualityCmaintenanceBridges coding agents with Roblox Studio, enabling inspection, generation, editing, and validation of Roblox places through natural language.MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with Roblox Studio via a token-efficient MCP server, live two-way script sync, and zero-friction plugin setup.-
TDQS
Scored across 22 tools
All tools have clearly distinct purposes. The map tools cover a complete pipeline (blockout, refine, validate, apply, readiness check), studio tools handle instance management, camera, properties, playtest, etc., and terrain is separate. No overlapping functionality.
Tool names follow a consistent pattern of prefix_group_action (e.g., map_create_blockout, studio_find_instances, terrain_generate). All use snake_case and descriptive names, making the set predictable and easy to navigate.
With 22 tools, the set is slightly above the typical well-scoped range (3-15), but given the breadth of Roblox Studio operations (map generation, instance management, camera, playtest, terrain), the count is still reasonable and not excessive.
The tool surface covers the full map generation lifecycle, comprehensive instance CRUD (via create, delete, patch, properties), camera control, playtest, terrain generation, and diagnostic tools. No obvious gaps for typical Studio automation tasks.