What Roblox Studio MCP Open Cloud Access Changed for Creators - 2026
If you searched roblox studio mcp open cloud after November 4, 2026, you do not need another “AI agents in Studio” hype post. You need a map of what actually changed: the new open_cloud_invoke tool, the MCP Permissions tab that scopes what an external client may call per game, three Skills that teach agents Open Cloud / permissions / import, and the hard line between place editing and monetization, publish, analytics, and asset upload from the same chat.
Roblox announced Studio MCP Server Updates: Open Cloud Access in Your MCP Client and Asset Import Workflows on November 4, 2026. Official how-to lives in Creator Hub Use Open Cloud with the Studio MCP server. The Weekly Recap: November 2–6, 2026 summarized the same ship for creators skimming the week.
This page is the what-changed read for creators, technical leads, and producers evaluating agent access. It is not a Stop opinion that refuses wide-open grants — that lives on Stop Granting Roblox MCP Open Cloud Without Per-Game Permissions - 2026. It is not a numbered free-checks listicle. It is not a fill-in permission worksheet. Those own refusal language, scorecards, and receipts. This URL owns the Studio MCP Open Cloud capability map.
Why this matters now
Before this update, Studio MCP was mainly a build-in-place bridge: edit instances, run Luau, playtest. After November 4, the same external MCP client (Claude Code, Cursor, Codex, and peers) can call Open Cloud through Studio without you pasting an API key into the agent. Studio signs requests with a token limited to the scopes you enabled for that game. That is a productivity unlock and a governance surface at once.
If your Monday standup still treats MCP as “the thing that writes scripts,” you are measuring last month’s product. Agents can now propose developer products, change place settings, publish, restart servers, read analytics, upload assets from approved folders, and — if you allow it — touch data stores or HTTP from execute_luau. The correct first question is not “which model is smartest?” It is “which scopes are on for this experience, for this human?”
Direct answer: Connect an external MCP client to Studio. Open MCP → MCP Permissions (or Assistant → … → Settings → MCP Permissions). Start from Safe or Balanced, not Full access. Enable only the sections the task needs. Use open_cloud_invoke for Open Cloud calls — the client never sees credentials. Use the new Skills for endpoint selection, missing-permission prompts, and Blender/Maya import repair. Do not confuse these controls with the built-in Studio Assistant — Roblox says these permissions and Skills apply to external MCP clients only.
Who this read is for
| Audience | Use it to… |
|---|---|
| Beginners | Name Open Cloud vs place edit; find the Permissions tab |
| Developers | open_cloud_invoke parameters, scopes, import folder rules |
| Creators | Discord brief: agents can touch money/settings under your scopes |
| Companies | Diligence — per-person permissions, Full access risk, upload permanence |
Time: 25 minutes to read. First permission + one dry-run evening: 60–120 minutes on a non-production place.
Honest limit: DevForum + mcp-open-cloud docs are authorities. Re-read before you freeze a studio policy. Known caveat from the weekly recap: unsaved places cannot add HTTP allow-list domains for execute_luau until you Save/Publish to Roblox.
Related catalog: Roblox Studio guide, Analytics Journeys what-changed, Fall roadmap lock, and the Unreal MCP loopback Stop for a parallel “don’t expose agents” mindset on another engine — Stop exposing Unreal Engine 5.8 MCP beyond loopback.
Non-repetition
| URL | Job |
|---|---|
| DevForum MCP Open Cloud announcement | Primary ship note |
| Use Open Cloud with Studio MCP | Official tool + permissions docs |
| Weekly Recap Nov 2–6 | Week summary + known HTTP issue |
| Journeys what-changed | Analytics paths — not MCP |
| Content serialization what-changed | File format / Rojo — not MCP |
| Stop Granting MCP Open Cloud Without Per-Game Permissions | Sibling refusal — Full access wallpaper |
| 12 Free MCP Open Cloud Checks | Sibling listicle — wire scorecard |
| MCP Open Cloud Permission Worksheet | Sibling fill-in PERMS_OK receipt |
| Unreal MCP loopback Stop | Different engine agent safety |
| Fall roadmap lock | Broad product ladder |
| Roblox Studio guide | Platform hub |
| 25 Discords | Paste channel |
| HTTP 403 help | Proxy while fetching tools |
| Courses | Learning ladder |
| This URL | What Studio MCP Open Cloud access changed |
The one-paragraph version
Studio MCP now exposes open_cloud_invoke so an external MCP client can call Open Cloud endpoints under https://apis.roblox.com with method, path, optional JSON body, optional scopes, and optional files from approved upload folders. Studio manages credentials — you do not need to hand the agent an Open Cloud API key. Access is gated by the MCP Permissions tab: per person, per game, with starting levels Safe / Balanced / Full access / Custom. Sections cover look/edit game, players & social, data stores, HTTP allow lists, asset publish, monetization, and more. Three Skills — rbx-open-cloud-usage, rbx-permissions, rbx-import-asset — teach agents to call Open Cloud, request only missing scopes, and import/fix GLB/FBX-style assets. Built-in Studio Assistant does not use these external MCP permissions. Uploads are permanent and moderated; you are responsible for what agents upload.
What existed before vs what shipped Nov 4
| Before | After Nov 4, 2026 |
|---|---|
| MCP focused on place creation / edit / playtest | Same chat can manage Open Cloud operations |
| External keys or Hub clicks for many ops | Studio-signed open_cloud_invoke under your scopes |
| Weak story for “agent set up a game pass” | Monetization + settings + analytics from chat |
| Ad-hoc import | Import Skill with scale/texture/anchor repair loop |
| No first-class per-game MCP scope UI for externals | MCP Permissions tab + access levels |
Capability 1 — open_cloud_invoke
Job: Name the tool so teams stop inventing fake “MCP Open Cloud” plugins.
Per Creator docs, parameters include:
| Parameter | Role |
|---|---|
method |
GET, POST, PUT, PATCH, or DELETE |
endpoint |
Path under https://apis.roblox.com, including query string |
body |
JSON-encoded body; omit for GET/DELETE |
scopes |
Optional list the endpoint needs (clearer errors if missing) |
files |
Local files for multipart uploads — must sit in an approved folder |
Studio enforces enabled scopes. The client never sees credentials. Only you can change permissions; the client cannot enable them alone.
Beginner check: If someone says “paste your Open Cloud key into Cursor,” that is the old mental model for many workflows. For Studio MCP Open Cloud, Roblox’s FAQ answer is: No API key required — Studio handles access limited to turned-on permissions.
Capability 2 — MCP Permissions tab (per person, per game)
Job: Make governance visible before the first agent session.
Open path (either):
- Click MCP in the bottom-right of Studio → MCP Permissions, or
- Assistant → … → Settings → MCP Permissions.
Permissions save to your account for each game. Collaborators set their own — enabling a scope for you does not enable it for them.
Access levels (starting points)
| Level | Intent |
|---|---|
| Safe | Low-risk scopes; most permissions off |
| Balanced | Default start — low + moderate risk |
| Full access | All scopes, including high-risk (Robux spend, live publish, player impact) |
| Custom | Shown after you tweak individual toggles |
Creator Discord paste: “Balanced is a start, not a forever policy. Full access is a deliberate choice with a named owner.”
Permission sections (what agents can do)
From the announcement and docs, sections include (names may expand — verify in Studio):
| Section | Examples of power |
|---|---|
| Look at your game | Read settings, version history, analytics |
| Edit your game | Change settings, publish, restart servers |
| Money & monetization | Developer products, game passes, related money APIs |
| Publish & manage assets | Upload models/images, check status |
| Save & load data | Data store / memory store from execute_luau when allowed |
| Connect to the internet | HTTP from Luau to allow-listed domains |
| Players & social / consequences | Social and moderation-related scopes (see live docs) |
Each section maps to Open Cloud scopes or script capabilities. Details: Open Cloud with Studio MCP and the Open Cloud scopes reference linked from that page.
Capability 3 — What you can do from the same chat
Announcement examples creators will quote:
- Set up a store — developer products and game passes with prices and icons.
- Change game settings — update game/place settings, publish, or restart servers without opening Creator Hub.
- Check how an update did — read analytics after publish.
- Pull data from your service — call an allow-listed API and use the response in the place.
That list is why this update is not “autocomplete for Luau.” It is operations surface area next to the script editor.
Capability 4 — Asset import workflow
Job: Separate “drop a mesh in” folklore from the moderated upload path.
Ask the agent to bring a model from Blender, Maya, or tools that export GLB/FBX-style assets into the open place. The flow exports, uploads, inserts, then compares against the source and fixes common import damage:
- Scale and rotation toward real-world size / source orientation
- Textures and colours restored when imports go grey
- Anchoring and placement on the ground, clear of other objects
Requirements called out by Roblox:
- Turn on Publish & manage assets
- Approve the folder exports live in
- Uploads are permanent and go through moderation like other assets
- Import Skill is designed to confirm with you before uploading
- You are responsible for uploads agents make on your account
Capability 5 — Three new Skills
| Skill | Job |
|---|---|
rbx-open-cloud-usage |
Call Open Cloud with open_cloud_invoke, pick endpoints, handle errors |
rbx-permissions |
Infer needed permissions, check which are on, ask only for missing ones |
rbx-import-asset |
Import from external 3D tools, then check/fix — builds on the other two |
Find them under Assistant → … → Assistant Settings → Skills. Duplicating a Skill lets you customize, but your copy will not receive future Roblox updates to the original.
Honest limit: Skills teach agents; they do not replace your permission choices. An agent that “asks for Full access” can still be refused.
Capability 6 — What did not change (trap list)
| Trap | Truth |
|---|---|
| “Assistant uses the same MCP Permissions” | External MCP clients only — not built-in Assistant |
| “One collaborator’s scopes cover the team” | Per person, per game |
| “No key means no risk” | Scopes can still publish and spend Robux |
| “Import is local only” | Uploads are permanent + moderated |
| “Unsaved place can allowlist HTTP” | Known issue — Save/Publish first, then add domains |
| “This replaces Creator Hub forever” | Hub and diligence still exist; chat is another path |
Audience ramps
Beginner path (forty minutes)
- Read the DevForum key takeaways once.
- Open a non-production experience in Studio.
- Open MCP Permissions — note Safe / Balanced / Full access.
- Leave Full access off.
- Connect your MCP client using current Studio MCP setup docs for your tool.
- Ask a read-only task first (look at game / analytics) after enabling only Look scopes.
- Paste Discord: “Open Cloud MCP is live. Permissions first. Full access is a meeting.”
Developer path (one evening)
- Skim mcp-open-cloud end to end.
- Map your CI/human seats: who may enable Edit / Money / Publish.
- Dry-run
open_cloud_invokewith a GET on a safe read endpoint. - Practice import on a throwaway folder with Publish & manage assets on.
- Document the unsaved-place HTTP caveat in your team runbook.
- Separate “Studio Assistant experiments” from “external MCP policy.”
- Add a PR template line: list scopes required for any agent-assisted Open Cloud change.
- Compare agent safety culture with the Unreal MCP loopback Stop — different stack, same refuse habit.
- After first week, review which scopes were actually used vs granted.
- Schedule a Stop / checks / worksheet sibling pass for refuse language and receipts (queued separately).
Creator Monday checklist
- [ ] Permissions tab opened on the live experience (not only a sandbox myth).
- [ ] Access level written: Safe / Balanced / Custom (avoid silent Full).
- [ ] Money & monetization off unless a named task needs it.
- [ ] Publish & manage assets off unless importing today.
- [ ] Upload folders listed and minimized.
- [ ] Collaborators told to set their own scopes.
- [ ] Import confirmation culture: humans approve uploads.
- [ ] Analytics read path tested after a publish (optional).
- [ ] Discord paste sent.
- [ ] Known HTTP allow-list caveat documented.
Opinion spine — what the change forces
| Folklore | After this map |
|---|---|
| MCP = script autocomplete | MCP = place + Open Cloud ops |
Keys in .env for Studio MCP Open Cloud |
Studio-signed token under scopes |
| One shared “studio AI login” | Per-person permissions |
| Full access for convenience | High-risk deliberate choice |
| Import = drag-drop forever | Moderated permanent upload |
| Assistant and MCP are the same policy | External clients only for this tab |
Quotable takeaway: November 4 moved Studio MCP from build-in-place to Open Cloud operations under per-game permissions you control — scopes first, Full access last.
Failure modes
| Failure | Symptom | Fix |
|---|---|---|
| Wide Full access | Agent publishes or spends unexpectedly | Drop to Balanced/Custom; revoke Money/Edit |
| Missing scope | Opaque or clear scope errors | Enable only required section; use rbx-permissions Skill |
| Upload from wrong folder | File rejected | Approve folder; keep exports there |
| Unsaved place HTTP | Cannot add domains | Save/Publish to Roblox first |
| Collaborator confusion | “It works for you” | Each person sets scopes |
| Treating Assistant as MCP | Wrong mental model | External clients only |
| Blame “corrupt place” after agent edit | No scope audit | Log which sections were on |
CapEx four-liner (diligence zip cover)
- Scope — Studio MCP Open Cloud via
open_cloud_invokeunder per-person, per-game MCP Permissions. - Cost — permission evening vs accidental publish/monetization from chat.
- Evidence — access level screenshot + scope list + dry-run log.
- Owner — named human who refuses Full access without a ticket.
Worked example — indie store setup evening
- Open non-prod copy; Balanced access.
- Enable Money & monetization temporarily.
- Ask agent to draft two game passes with prices — review before confirm.
- Disable Money section when done.
- Enable Look at your game; ask for a settings/analytics read.
- File screenshots: scopes before/after.
Worked example — Blender prop import
- Enable Publish & manage assets; approve
~/exports/roblox/. - Export GLB from Blender into that folder.
- Ask agent to import with
rbx-import-assetSkill; confirm upload prompt. - Verify scale/textures/anchor in Studio.
- Disable Publish section if no more uploads today.
Scheduling table
| When | Action |
|---|---|
| Week of Nov 4 | Read announcement + docs; set Balanced baseline |
| First agent week | Read-only scopes → write scopes with owner |
| Ongoing | Audit Full access; minimize upload folders |
| Policy freeze | CapEx four-liner in partner zip |
How this pairs with other November Roblox posts
| Topic | Job |
|---|---|
| Content serialization / Rojo | Disk format tooling cliff |
| Journeys | Analytics path modeling |
| This URL | MCP Open Cloud capability map |
| Stop · Checks · Worksheet | Refusal, scorecard, PERMS_OK receipt |
Do not paste this essay as proof permissions are locked. Paste a scope screenshot.
Internal links
Platform hub: Roblox Studio guide. Analytics sibling: Journeys what-changed. Roadmap: Fall lock. Agent safety parallel: Unreal MCP loopback Stop. Help: HTTP 403. Resources: 25 Discords. Courses: /courses.
Key takeaways
- Nov 4, 2026 — Studio MCP gains Open Cloud via
open_cloud_invoke. - No Open Cloud API key required for this path — Studio signs under your scopes.
- MCP Permissions are per person, per game.
- Start Safe/Balanced; treat Full access as high risk.
- Same chat can touch monetization, settings, publish, analytics, imports.
- Skills:
rbx-open-cloud-usage,rbx-permissions,rbx-import-asset. - External MCP clients only — not built-in Assistant.
- Uploads are permanent and moderated; you own agent uploads.
- Unsaved places block HTTP allow-list adds until Save/Publish.
- Collaborators do not inherit your scopes.
- CapEx four-liner belongs in diligence zips.
- Quotable: scopes first, Full access last.
- This URL owns the capability map — not the Stop/checks/worksheet.
- Re-read DevForum + Creator docs when scopes expand.
- Dry-run read scopes before write/money scopes.
FAQ
When did Studio MCP Open Cloud access ship?
November 4, 2026, per Roblox’s DevForum announcement.
Do I need an Open Cloud API key?
No for Studio MCP Open Cloud — Studio handles access limited to permissions you enable for that game.
Where do I set permissions?
MCP button → MCP Permissions, or Assistant → … → Settings → MCP Permissions.
Do my scopes apply to collaborators?
No. Each collaborator sets their own permissions per game.
Does this apply to Studio Assistant?
No. These permissions and Skills apply to external MCP clients only.
What is open_cloud_invoke?
The MCP tool that calls Open Cloud endpoints (method, endpoint, body, scopes, files) under Studio-enforced permissions.
What are the new Skills?
rbx-open-cloud-usage, rbx-permissions, and rbx-import-asset.
Can agents upload assets?
Yes if Publish & manage assets is on and the folder is approved. Uploads are permanent and moderated.
Why can’t I add HTTP domains?
Known issue on unsaved places — Save or Publish to Roblox first, then add domains under Connect to the internet.
Is Full access required?
No. Prefer Safe/Balanced and enable only needed sections.
Where is the official documentation?
Use Open Cloud with the Studio MCP server
How is this different from Analytics Journeys?
Journeys model player paths in Creator Hub. This page is about agent Open Cloud operations through Studio MCP.
Sources
- Studio MCP Server Updates: Open Cloud Access… (DevForum)
- Use Open Cloud with the Studio MCP server (Creator Hub)
- Weekly Recap: November 2–6, 2026 (DevForum)