THE SHORT ANSWER
Roblox has added three new tools to the Studio MCP Server: screen_capture now records video during playtests so agents can verify motion and timing; save_place lets agents save work with version-history notes without publishing; and submit_feedback sends tool-error reports straight to the Studio team. Agents using MCP will adopt these automatically. Publishing via API is planned for future releases.
- screen_capture records video for animation smoothness, flicker, and timing checks — screenshots remain default for cost
- save_place writes versioned saves with notes (e.g., "Fixed door open stutter") for both cloud and local places; first save requires manual action
- submit_feedback transmits tool failures only — no source code, credentials, or personal data — and notifies the creator each time
- Publishing via MCP API is the next major gap the Studio team plans to close in coming months
Video Capture Adds Motion Testing to Agent Workflows
The screen_capture tool previously returned static screenshots. Now it can record video during a playtest, letting an agent see whether an animation stutters, a tween eases correctly, or a UI element flickers across frames. The agent can play, record, apply a fix, then record again to confirm the change — without the creator watching each attempt. Screenshots remain the default because they are cheaper; video is triggered only when a still frame cannot answer the question or when the creator explicitly requests a recording. Example use cases from the announcement include smoothing a jittery walk cycle, catching lighting flicker, and verifying that a door opens, a sound plays, or a hit registers at the correct moment.
Save_place Lets Agents Commit Changes Without Publishing
Until this update, agents could modify a place but could not persist those changes. Save_place performs the equivalent of Ctrl+S: it saves the place to Roblox (including Team Create sessions) or to a local file, adds a creator-visible note such as "Added double jump to PlayerController," and writes an entry to version history. It never publishes, so players see nothing until the creator publishes manually. If a place has never been saved, Studio prompts the creator to save it once; afterward the agent handles subsequent saves. The version history makes it straightforward to roll back to the state before an agent change.
Submit_feedback Routes Tool Errors Straight to the Studio Team
When a Studio tool fails during an agent session, the details typically stay in the chat log. Submit_feedback lets the agent send a short report — what went wrong and what would have worked better — directly to the Studio team. Reports cover Studio and its built-in tools only; they exclude source code, personal information, and credentials. The agent informs the creator each time it sends a report and stops if the creator tells it to.
What This Means for Creator Workflows
The three tools chain together in a single request. A creator can ask an agent to fix a stuttering door animation. The agent playtests, records the door opening, spots the stutter, adjusts the animation, records again to confirm smooth motion, saves with a descriptive note, and — if any tool misbehaved along the way — files a feedback report and notifies the creator. The creator receives a fixed door and a labeled version to revert to, without having to playtest by hand or write a bug report.
Publishing API Next on the Roadmap
The Studio team says the next focus is opening more Studio APIs to the MCP Server, starting with publishing. Publishing is currently the step creators must still perform manually. The team plans to roll out additional APIs in the coming months and is asking creators to identify which Studio actions they still have to do by hand during agent sessions.