Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Let your agent build inside Roblox Studio

Written November 8, 2026

Roblox Studio ships its own MCP server, and community servers add playtests, screenshots, and Luau execution. What each does, and which one to install first.

The problem

A Roblox developer wants an AI agent to build, test, and debug a game inside Studio — read scripts, run Luau, start a playtest, read the errors — and there are now four ways in: Studio's own server plus three community servers. No one of them does everything, and they differ most in playtesting: whether the agent can watch the game run, see the screen, and drive it like a player.

Studio's own server: install this first

Roblox ships an MCP server built into Studio. Enable it from Assistant → Manage MCP Servers; there is no separate install and no Rust toolchain. The transport is stdio, through the StudioMCP binary bundled with Studio, and quick connect supports Claude Code, Cursor, Codex CLI, Claude Desktop, Gemini CLI, VS Code, and Antigravity. Every tool call takes a studio_id, so one client can drive several open Studio instances.

What it exposes: execute_luau to run Luau in the open place, script_read, multi_edit, script_search and script_grep for scripts, search_game_tree and inspect_instance for the scene. Playtest automation covers starting and stopping play, mouse and keyboard input, character navigation, and screen capture. Asset generation covers generate_mesh, generate_material, and generate_procedural_model.

One warning carries over from Roblox's own docs: treat every connected MCP client as having write access to your open place, and only connect clients you trust.

roblox-mcp-pro: 29 tools, and it sees what it builds

roblox-mcp-pro is an open-source MCP server under the MIT license. It gives Claude, Codex, Cursor, and Antigravity hands-on control of a live Studio session: run Luau, query and mutate the DataModel, build UI, terrain, and lighting, take viewport screenshots, and keep a two-way Studio-to-local-file mirror. Its 29 tools include execute_luau, manage_scripts, manage_ui, manage_studio (playtests: Run mode and real Play Solo and multiplayer with test scripts and auto reports), and capture_studio, which screenshots the real viewport so the agent closes the loop instead of building blind. A live dashboard at 127.0.0.1:3690 shows connected agents, plugin status, the command queue, and sync state.

Install is two commands for Claude Code: claude mcp add roblox-mcp-pro -- npx -y roblox-mcp-pro@latest, then npx roblox-mcp-pro@latest install-plugin. The plugin self-installs on first run and self-updates on each launch. Multiple agents can drive the same Studio session at once through one shared broker.

Meganugger's roblox-studio-mcp: 68 tools and per-peer debugging

roblox-studio-mcp is a production-oriented integration, also MIT-licensed, with 68 tools. Its distinguishing feature is runtime debugging per peer: during a play-solo or multiplayer test, every DataModel connects as its own peer, so the agent can run eval_server_runtime and eval_client_runtime to inspect live game state mid-playtest, read each side's logs and errors with Luau stack traces, and set log breakpoints that instrument code without pausing. It can also operate Studio itself — get_host_capabilities, create_place_file, and launch_studio create a real .rbxlx project and open it, so a session needs no human setup step. It offers stdio for local clients plus a Streamable HTTP transport for AI platforms that only accept a server URL, and it can publish a place through Open Cloud — off by default and gated behind your own API key.

Setup is heavier than the other two: clone the repository, npm install, npm run build, install the Studio plugin with node server/dist/index.js --install-plugin, then add the server to your client config with an absolute path to the built server.

Kiet1308's studio-rust-mcp-server fork: playtests like a real player

studio-rust-mcp-server is an actively developed fork of Roblox's original Rust MCP server, which Roblox no longer develops. The fork adds full end-to-end play-testing: screenshots, UI inspection and search, real mouse and keyboard input, character control, camera control, and ProximityPrompt discovery. Its play-testing tools include take_screenshot, get_ui_tree, find_ui, click_ui and click_object through the engine's real input pipeline, send_key and send_text, and control_character to move, walk, and jump. Clicks are hit-tested before they are sent, so a popup covering the target fails the call naming the covering element instead of silently clicking the wrong thing. Install with release binaries on Windows, or build from source on macOS. It is MIT-licensed.

Which one to install first

None of the three community servers is official. That matters for trust — each one runs code inside your open place — and for longevity: Roblox replaced its own open-source server with the built-in one, and the Kiet1308 fork exists precisely because the original stopped being developed.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Agent-desktop drives apps via the access tree · Gemini Computer Use is generally available · Tencent Hy4: vision and computer use, weights pending