Evidence note: This report rests on Roblox’s own developer-forum posts — a Studio MCP announcement thread and the weekly recap for August 17–21, 2026. These are primary vendor sources describing Roblox’s own product. The behavior described has not been independently corroborated outside those posts, so specific claims below are attributed to Roblox rather than presented as externally verified. Where a figure or mechanism is not spelled out in the source, that gap is noted rather than filled in.
What the Studio MCP Server does
The Studio MCP Server is Roblox’s bridge between AI agents and Roblox Studio. According to Roblox, it lets developers connect MCP-enabled AI agents to Studio and make changes directly to Studio sessions (source). MCP — the Model Context Protocol — is the interface an external agent uses to discover and call tools; here, those tools act on a live Studio session rather than on files or a sandbox.
That framing matters for everything that follows: because the tools reach into a running Studio session, which session a call lands in is a correctness question, not a cosmetic one.
The change: every Studio MCP tool now takes a studio_id
Roblox announced that every Studio MCP tool now takes a studio_id, so agents address Studios explicitly instead of relying on session state (source). In practice, the target Studio becomes a parameter of each individual tool call. Roblox describes the routing as now explicit: each call must specify the Studio it targets rather than inheriting a previously selected one (per Roblox’s announcement).
How routing worked before: set_active_studio bound one client to one Studio
Before this release, an MCP client was bound to a single Studio instance through the set_active_studio tool, according to Roblox (per Roblox’s announcement). Under that model, a client selected a Studio once, and subsequent tool calls were understood to apply to whatever Studio the connection had last been pointed at — a piece of session state held on the connection rather than restated on each call.
Why shared connections failed: agents couldn’t reliably address different Studios
Section note: this is the load-bearing rationale for the change, and it is stated as Roblox’s characterization of the prior behavior, not an independently observed failure.
Roblox says that before this release, if several agents shared a single MCP connection, they couldn’t reliably address different Studios (per Roblox’s announcement). The reason follows from the earlier model: when the target Studio lives in connection-level state, two agents on the same connection contend over that single selection. One agent’s set_active_studio silently changes where the other agent’s next call will land. The address is shared even though the intent is not.
Explicit per-call routing over session state
The fix Roblox describes trades session state for an explicit argument. Instead of "select a Studio, then act," the pattern becomes "name the Studio in the act itself." Because the studio_id travels with each call, two agents sharing one connection no longer overwrite each other’s target — each call is self-describing (per Roblox’s announcement). This is the same distinction, in miniature, between an implicit "current directory" and passing an absolute path: the second is verbose but unambiguous under concurrency.
Why this matches how stateless MCP servers are meant to work
Roblox frames the explicit per-call routing as matching how stateless MCP servers are meant to work (per Roblox’s announcement). A stateless server keeps no per-connection memory of "which Studio is active" between calls, so each request must carry everything needed to route it. Moving the Studio target out of connection state and into the call parameters aligns the tool surface with that expectation. The trade-off it addresses — where to hold agent context — is a recurring one across AI-agent infrastructure; readers weighing the opposite design can compare Roblox’s stateless-leaning move here with the persistent-compute model described in our look at Runtime Instances on Amazon Bedrock AgentCore, which keeps agent state alive between calls rather than restating it each time.
More reliable workflows with multiple Studio instances and multiple clients
Roblox states that the explicit-routing change makes workflows with multiple Studio instances and multiple clients more reliable (per Roblox’s announcement). The improvement is scoped to exactly the case the old model strained under: more than one Studio open, or more than one agent connected, where the previous single-selection binding could send a call to the wrong session. Roblox’s post presents this as a reliability gain rather than a performance one; no throughput or latency figures are given (source does not provide them).
Assistant Settings now shows connected AI clients
Alongside the routing change, Roblox says Assistant Settings now shows connected AI clients (source). This surfaces which external agents are currently attached to a session — useful visibility in exactly the multi-client setups the routing change is meant to support, though the announcement does not detail what controls, if any, accompany that view (source does not specify).
Two stability issues fixed in this release
Roblox reports that this Studio MCP release fixed two stability issues (evidence: Roblox’s own announcement; the "two" is Roblox’s count, not an independently verified tally). The specific nature of those two fixes is not described in the sources reviewed, so their scope and severity remain open (source does not detail them).
Connected MCP clients pick up the change automatically
According to Roblox, connected MCP clients pick up the change automatically (per Roblox’s announcement) — meaning the new per-call routing takes effect without a manual client update on the developer’s part. The announcement does not spell out the mechanism behind that automatic adoption (source does not specify), so the practical note for developers is narrower: existing connected clients are expected to move to the new behavior on their own.
Timeline: the week of August 17-21, 2026
Roblox’s weekly recap places this update in the week of August 17–21, 2026, listing Studio MCP as having gained more reliable multi-agent workflows during that week (source). The Studio MCP changes shipped as one item among several creator-facing updates in that recap; the broader slate from the same week is covered in our roundup of Roblox creator updates for August 17–21, 2026.