Early versions of Roblox Studio MCP exposed separate, single-purpose tools for each playtest lifecycle event:Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Chrrxs/robloxstudio-mcp/llms.txt
Use this file to discover all available pages before exploring further.
start_playtest, stop_playtest, and a family of multiplayer_test_* tools for each multiplayer action. As the feature set grew, these split tools became hard to discover and their semantics were not always obvious. They were consolidated into two unified tools — solo_playtest and multiplayer_playtest — each of which accepts an action parameter to select the lifecycle operation.
The deprecated tools are still callable by exact name for existing integrations that depend on them. However, they are no longer advertised through tools/list. An agent that discovers available tools by calling tools/list will not see these names and must use the unified replacements for all new integrations.
Migration table
| Deprecated tool | Unified replacement |
|---|---|
start_playtest | solo_playtest action="start" |
stop_playtest | solo_playtest action="stop" |
multiplayer_test_start | multiplayer_playtest action="start" |
multiplayer_test_state | multiplayer_playtest action="status" |
multiplayer_test_add_players | multiplayer_playtest action="add_players" |
multiplayer_test_leave_client | multiplayer_playtest action="leave_client" |
multiplayer_test_end | multiplayer_playtest action="end" (disabled — see below) |
Deprecated tool descriptions
start_playtest
Started a solo Studio playtest. Replaced by solo_playtest action="start" mode="play" (or mode="run" for a server-only run). The unified tool adds an explicit mode field, a configurable timeout, and an action="status" query path — none of which were available on the split tool.
stop_playtest
Stopped the active solo playtest. Replaced by solo_playtest action="stop". The unified tool adds a configurable stop timeout.
multiplayer_test_start
Started a StudioTestService multiplayer playtest with a given number of client players. Replaced by multiplayer_playtest action="start" numPlayers=N force=true. The unified tool adds the force acknowledgement flag (see note below), a testArgs field for passing data to StudioTestService:GetTestArgs(), and a configurable timeout.
multiplayer_test_state
Returned the current multiplayer playtest state. Replaced by multiplayer_playtest action="status". The unified tool name better matches the convention used for solo_playtest.
multiplayer_test_add_players
Added additional client players to a running multiplayer session. Replaced by multiplayer_playtest action="add_players" numPlayers=N.
multiplayer_test_leave_client
Removed a specific client from a running multiplayer session. Replaced by multiplayer_playtest action="leave_client" target="client-N". The unified tool defaults to target="client-1" when target is omitted.
multiplayer_test_end
Attempted to call StudioTestService:EndTest() to stop the multiplayer session programmatically. This always returned a disabled error — StudioTestService:EndTest() is broken in the MCP flow and cannot be used to cleanly end a multiplayer test session. The replacement, multiplayer_playtest action="end", preserves this behavior: it still returns the disabled error and the same broken-API reason. Multiplayer test windows must be closed manually regardless of which tool name is used.