roblox-studio-bridge MCP
Related Servers
Alternatives to roblox-studio-bridge MCP
No user-submitted related servers found.
Related Servers
- 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.5027 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,042 npmMIT
- AlicenseAqualityCmaintenanceEnables AI coding tools to control Roblox Studio for workspace exploration, instance manipulation, and script management. It provides tools for playtesting, scene rendering, and integration with the Roblox Creator Store.68MIT
- 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.9MIT
- 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 gradedqualityAmaintenanceEnables AI assistants to control Roblox Studio by running Luau code, creating and editing instances, reading the scene tree, and managing scripts via an MCP server with a long-polling plugin bridge.MIT
TDQS
Scored across 11 tools
Each tool targets a distinct capability: session listing, code execution, logs, screenshots, project sync, test lifecycle, GUI inspection, plugin reload, and tree traversal. Even where run_luau returns print output, get_logs is clearly the historical log reader, so no two tools are easily confused.
Most tools follow a clear verb_noun snake_case pattern such as run_luau, start_test, stop_test, add_players, and get_tree. Minor deviations like studio_status (noun phrase) and screenshot (single word without object) keep it from being perfectly consistent.
Eleven tools is well within the ideal range for a domain-specific server, and each tool covers a meaningful part of the Roblox Studio workflow without redundancy or bloat.
The surface covers session discovery, arbitrary Luau execution, log access, visual inspection, project syncing, test lifecycle management, simulated players, GUI hierarchy listing, and instance tree traversal. run_luau also provides a powerful escape hatch for any specialized operation not explicitly exposed.