Roblox expands Studio MCP with Open Cloud access and asset imports
Roblox adds Open Cloud calls and asset import workflows to Studio MCP. Review per-game permissions before letting external agents change settings or upload assets.
Roblox expanded Studio’s MCP server on November 4, 2026, letting external MCP clients call Open Cloud through open_cloud_invoke and import models from external tools. According to the November 4, 2026 announcement, developers can use connected agents to manage products, passes, settings, publishing, and analytics. These permissions and Skills apply only to external clients, not Studio’s built-in Assistant.
Permissions define the working boundary
Roblox says permissions are stored separately for each person and game; collaborators must configure their own. Only the user can change them in Studio. Controls cover API scopes, upload folders, data access, and allowed internet domains. Studio handles authentication without an Open Cloud API key, but some endpoints reject its MCP token even when permission is enabled. Those calls require a Studio-tool alternative or Creator Dashboard.
Our recommendation is to start this week with an analytics-reading task, leaving publishing and monetization permissions off. Open MCP Permissions from Studio’s bottom-right MCP indicator and check access against the permissions documentation. Roblox’s Skills instruct agents to request confirmation for sensitive actions; that guidance is distinct from the permissions users control.
Test imports before routine use
Roblox also added three Skills covering Open Cloud, permissions, and asset imports, automatically accessible to connected agents. The import workflow exports, uploads, inserts, and checks models from tools such as Blender or Maya, including scale, rotation, textures, and placement. It requires Publish & manage assets permission and approval for the export folder.
We’d start by comparing a test import with its source. Roblox says uploads are permanent, moderated, and owned by the game owner, including a group where applicable. Developers remain responsible for agent uploads. Open Cloud cannot delete or archive models or images; removal requires Creator Dashboard.