12 Free Roblox Studio MCP Open Cloud Checks Before You Wire Agents - 2026
![]()
If you searched roblox mcp open cloud checks after November 4, 2026, you already have a what-changed map and a Stop on Full access wallpaper. What was missing is a numbered free preflight kit: twelve pass/fail checks before anyone connects Claude Code, Cursor, or Codex and lets open_cloud_invoke touch monetization, publish, analytics, or permanent uploads.
Roblox announced Studio MCP Server Updates: Open Cloud Access in Your MCP Client and Asset Import Workflows. Official how-to lives in Use Open Cloud with the Studio MCP server. The Weekly Recap: November 2–6, 2026 flags a known HTTP allow-list caveat on unsaved places.
This listicle owns the free checks kit. It is not the capability curriculum. It is not the Stop opinion. It is not the fill-in permission worksheet. Those own map, refusal, and evening receipts. This URL owns pass/fail checks before you wire agents to Open Cloud.
Why this matters now
Leads flip Full access, paste a client config, ask the agent to “set up the store,” and then argue about whether Studio or the model “broke the economy.” Or they leave Publish & manage assets on forever, approve the whole Documents folder, and wonder why an import session felt spooky. Or they try to allowlist HTTP domains on an unsaved place and file a Sev-1 that “MCP networking is broken.” The board hears “AI tools are flaky.” You skipped the kit.
Direct answer: Run checks 1–4 before you connect any external MCP client. Run 5–9 before the first write or import. Run 10–12 before anyone claims the agent is “production-ready.” If check 2 fails (Full access without a ticket), stop — reread the Stop on per-game permissions. Authority: DevForum announcement + Creator Hub docs + Weekly Recap.
Who this list is for
| Audience | Use it to… |
|---|---|
| Beginners | Four-check minimum before agent FOMO |
| Developers | Scope matrix, Skills, upload folders, HTTP save caveat |
| Creators | Paste a twelve-check card into Discord |
| Companies | Diligence — wired agent ≠ audited Open Cloud SLA |
Time: 25 minutes for 1–4; 90–150 minutes for full write/import smokes on a non-prod place.
Honest limit: Official docs win if this page drifts. Skills and section names can expand — re-open the Permissions tab before you freeze a policy.
Related catalog: Roblox Studio guide, MCP what-changed, Stop Granting Without Permissions, and the Unreal parallel refuse — Stop exposing Unreal MCP beyond loopback.
Non-repetition
| URL | Job |
|---|---|
| MCP Open Cloud what-changed | Capability map |
| Stop Granting Without Permissions | Refusal / Full access Stop |
| MCP Open Cloud Permission Worksheet | Fill-in PERMS_OK receipt |
| DevForum MCP Open Cloud | Primary ship note |
| Creator Hub mcp-open-cloud | Official tool + permissions |
| Weekly Recap Nov 2–6 | HTTP allow-list caveat |
| Unreal MCP loopback Stop | Different stack refuse |
| Journeys checks | Analytics preflight — not MCP |
| Fall roadmap | Broad ladder |
| Roblox Studio guide | Platform hub |
| 25 Discords | Paste channel |
| HTTP 403 help | Proxy while fetching tools |
| Courses | Learning ladder |
| This URL | Numbered MCP Open Cloud checks |
Four-check minimum (twenty-five minutes)
| # | Check | Fail means |
|---|---|---|
| 1 | Read mcp-open-cloud + DevForum takeaways once | Myths about “no key = no risk” |
| 2 | Access level is Safe/Balanced (Full access refused) | Wallpaper governance |
| 3 | Money & Publish assets off unless named task | Accidental store/upload |
| 4 | EXTERNAL_MCP latch written (not Assistant folklore) | Wrong policy surface |
Do not “wire the agent and celebrate” until these four are green — and do not skip 5–12 before partner claims.
Selection criteria
A check is in only if all are true:
- Free — Studio / Creator Hub / docs only.
- Primary job is safe MCP Open Cloud enablement — scopes, Skills, import, or refuse false wiring.
- Grounded in the Nov 4 announcement, mcp-open-cloud docs, or Weekly Recap.
- Honest limits in one sentence.
- Useful before anyone lets an agent write Open Cloud.
Preflight cheat sheet (read before check 5)
| Rule | Source truth |
|---|---|
open_cloud_invoke under Studio-signed scopes |
mcp-open-cloud docs |
| No Open Cloud API key required for this path | DevForum FAQ |
| Permissions per person, per game | DevForum + docs |
| Safe / Balanced / Full / Custom levels | docs |
| External MCP clients only — not Assistant | DevForum FAQ |
| Uploads permanent + moderated | DevForum import section |
| Unsaved place → cannot add HTTP domains | Weekly Recap known issue |
Skills: rbx-open-cloud-usage, rbx-permissions, rbx-import-asset |
DevForum |
Curriculum depth lives on the what-changed map. Refusal language lives on the Stop. This kit forces you to prove each gate.
Scorecard (print or paste)
| # | Check | Pass / Fail | Owner | Note |
|---|---|---|---|---|
| 1 | Docs latch | |||
| 2 | Access level refuse Full | |||
| 3 | Money + Publish assets default off | |||
| 4 | External MCP vs Assistant latch | |||
| 5 | Look-only dry-run | |||
| 6 | Collaborator seats set own scopes | |||
| 7 | Skills present / understood | |||
| 8 | Upload folder minimized | |||
| 9 | Import confirm culture | |||
| 10 | HTTP place saved before allow-list | |||
| 11 | Time-box revoke after elevated task | |||
| 12 | CapEx four-liner + screenshot |
Wire gate: Do not connect a write-capable agent session until 1–4 pass. Do not claim production-ready until 1–12 pass on the target experience (or a documented non-prod twin).
The twelve checks
1. Docs latch (mcp-open-cloud + DevForum)
Do: Open Use Open Cloud with the Studio MCP server and the DevForum announcement. Note open_cloud_invoke, per-person permissions, access levels, Skills names, and “no API key” FAQ.
Pass: Written note: “Studio-signed scopes; Full access high risk; external clients only.”
Fail: “No key means free power / Assistant uses the same tab.”
Honest limit: Section lists can grow — re-read before policy freeze.
2. Access level refuse (Full access is a ticket)
Do: Open MCP → MCP Permissions (or Assistant → … → Settings → MCP Permissions). Record Safe / Balanced / Full / Custom. If Full, switch to Balanced unless a named ticket exists (see Stop).
Pass: Screenshot shows Safe, Balanced, or documented Custom — not silent Full.
Fail: Full access “just for the demo.”
Honest limit: Balanced is a start, not forever — still audit sections.
3. Money & Publish assets default off
Do: Confirm Money & monetization and Publish & manage assets are off unless today’s task needs them. Edit/publish scopes off for read-only evenings.
Pass: High-blast sections off; Discord note of what is allowed today.
Fail: All sections green because “the agent might need them.”
Honest limit: You can enable temporarily — this check refuses default on.
4. External MCP vs Assistant latch
Do: Write one line in the runbook: “MCP Permissions apply to external MCP clients only; Studio Assistant is a separate policy.”
Pass: Latch present; onboarding does not merge the two.
Fail: “We set the tab so Assistant is locked down.”
Honest limit: Assistant still has its own powers — this check only stops category errors.
5. Look-only dry-run before writes
Do: Enable Look-related scopes only. Connect the client. Ask for a read of game/settings/analytics as appropriate. Confirm a successful read path before enabling Edit or Money.
Pass: Dry-run log with timestamp + scopes list.
Fail: First prompt is “create a game pass on the live place.”
Honest limit: Analytics reads need the matching Look scopes — enable deliberately.
6. Collaborator seats set their own scopes
Do: Ask every human who will use MCP on this game to open Permissions and set their own level. Do not assume the lead’s scopes cover contractors.
Pass: Seat checklist with initials.
Fail: “Lead enabled Full so we’re good.”
Honest limit: Per Roblox, enabling for you does not enable for anyone else — and vice versa.
7. Skills present and understood
Do: Assistant → … → Assistant Settings → Skills. Confirm awareness of rbx-open-cloud-usage, rbx-permissions, rbx-import-asset. Note that duplicates stop receiving upstream updates.
Pass: Team knows Skills teach agents; humans still grant scopes.
Fail: “Skills mean we can click Full safely.”
Honest limit: Skill availability depends on connected MCP client behavior — verify in your tool.
8. Upload folder minimized
Do: If Publish & manage assets will be on, approve only the export folder (e.g. ~/exports/roblox/), not Desktop/Documents/home.
Pass: Folder path written; home directory not approved.
Fail: Entire user profile approved “for convenience.”
Honest limit: Files must live in approved folders for multipart uploads.
9. Import confirm culture
Do: Agree that humans confirm uploads. Roblox notes the Import Skill is designed to confirm before uploading; uploads are permanent and moderated; you own agent uploads.
Pass: Written “no silent upload” rule in Discord/runbook.
Fail: “Just let it import overnight.”
Honest limit: Moderation and permanence still apply after confirm.
10. HTTP place saved before allow-list
Do: If you need Connect to the internet / domain allow-lists for execute_luau, Save or Publish the place to Roblox first. Weekly Recap: unsaved places cannot add HTTP domains.
Pass: Place is saved/published; then domains added.
Fail: Filing “MCP HTTP broken” on an unsaved place.
Honest limit: This is a known issue — do not invent custom networking folklore.
11. Time-box revoke after elevated task
Do: After a store or import evening, disable Money / Publish assets / wide Edit the same day. Screenshot before and after.
Pass: Revoke timestamps in the ticket.
Fail: Elevated scopes left on for “next week.”
Honest limit: Custom level after tweaks is fine — forever-on high-blast is not.
12. CapEx four-liner + Permissions screenshot
Do: File the diligence cover: (1) Scope — per-person MCP Permissions on this experience; (2) Cost — permission evening vs accidental publish/spend/upload; (3) Evidence — screenshot + enabled sections; (4) Owner — named human. Attach to the wire ticket.
Pass: CapEx block + screenshot in the same message/PR.
Fail: “We’ll document after the jam.”
Honest limit: Screenshots age — re-capture after major scope changes.
Audience ramps
Beginner path (forty minutes)
- Run checks 1–4 on a non-prod experience.
- Paste the four-check minimum table into Discord.
- Do not connect a write agent until 2 and 3 pass.
- Read the Stop refuse codes once.
- Schedule checks 5–12 for the next evening.
Developer path (one evening)
- Complete 1–12 on the target experience (or twin).
- Dry-run Look (5) then a temporary Money enable/disable drill (11).
- Practice import folder approval (8–9) without leaving Publish on.
- Document HTTP save order (10) in the team wiki.
- Link CapEx four-liner (12) from the partner zip template.
- Cross-link what-changed for parameter depth.
- Compare refuse culture with Unreal MCP Stop.
- Add scorecard columns to your PR template for agent-assisted Open Cloud changes.
Creator Monday checklist
- [ ] Checks 1–4 green before wire.
- [ ] Full access refused without ticket.
- [ ] Money/Publish assets off by default.
- [ ] Collaborators reminded to set own scopes.
- [ ] Upload folder named if importing.
- [ ] Place saved before HTTP allow-list.
- [ ] Discord paste: “Twelve MCP checks — wire only when green.”
- [ ] CapEx + screenshot filed when partners ask.
Failure modes the kit catches
| Failure | Missed check | Symptom |
|---|---|---|
| Silent Full access | 2 | Unexpected publish/spend |
| Forever Money on | 3, 11 | Store drift from chat |
| Wide upload root | 8 | Sensitive file eligibility |
| Assistant/MCP merge | 4 | Wrong policy debates |
| Unsaved HTTP rage | 10 | False “networking broken” |
| Collab assumed | 6 | “Works for lead only” folklore |
| No evidence | 12 | Diligence fails |
CapEx four-liner (diligence zip cover)
- Scope — Studio MCP Open Cloud under per-person, per-game permissions; twelve-check wire gate.
- Cost — preflight evening vs accidental Open Cloud writes from chat.
- Evidence — filled scorecard + Permissions screenshot.
- Owner — human who refuses wire when any of 1–4 fail.
Worked example — indie wiring night (non-prod)
- Open a non-production copy of the experience.
- Run checks 1–4; Discord paste the four-check minimum.
- Connect Cursor/Claude with Look scopes only (check 5).
- Ask for a read of place settings or analytics — no Money.
- Temporarily enable Publish & manage assets; approve
~/exports/roblox/only (8–9). - Import one throwaway GLB with human confirm; then revoke Publish (11).
- File CapEx + screenshots (12). Latch wire-ready for non-prod only.
Worked example — live store task without wallpaper
- Ticket: “Add two game passes for weekend sale.”
- Checks 1–4 already green from Monday.
- Enable Money & monetization for this seat only.
- Agent drafts products; human confirms prices/icons in Hub or chat.
- Disable Money immediately; screenshot after.
- Checks 11–12 updated on the ticket. Live Edit/publish stays off unless a separate publish ticket exists.
If the agent asks for Full access mid-task, fail check 2 again. Prefer enabling the one section the endpoint needs. The rbx-permissions Skill is supposed to ask for missing scopes — your job is to refuse the ones that are not missing for this task.
Red flags that mean “stop wiring”
| Red flag | Action |
|---|---|
| Permissions tab never opened on this experience | Fail 2 — open it now |
| Home directory approved for uploads | Fail 8 — shrink folder |
| “Assistant is locked so MCP is fine” | Fail 4 — rewrite latch |
| First prompt creates products on live | Fail 5 — dry-run first |
| Contractor told “use the lead’s setup” | Fail 6 — each seat sets scopes |
| HTTP allow-list attempted on unsaved place | Fail 10 — Save/Publish first |
These flags are cheaper than a postmortem. Use them in standup when someone says “AI broke our store.” Print the scorecard once, keep it next to the MCP button, and treat a failed row like a failed build — no wire until green.
Monday sequence (ninety minutes)
| Minute | Action |
|---|---|
| 0–15 | Checks 1–4 + Discord paste |
| 15–35 | Check 5 Look dry-run |
| 35–50 | Checks 6–7 seats + Skills |
| 50–70 | Checks 8–9 folder + import culture (even if not importing) |
| 70–80 | Check 10 save/publish if HTTP needed |
| 80–90 | Checks 11–12 revoke plan + CapEx |
How this pairs with sibling URLs
| Topic | Job |
|---|---|
| MCP what-changed | Capability map |
| Stop Granting Without Permissions | Refusal |
| This URL | Pass/fail scorecard |
| MCP Open Cloud Permission Worksheet | Fill-in PERMS_OK receipt |
Do not paste this listicle as proof scopes are locked. Paste a filled scorecard + screenshot.
Internal links
Map: Studio MCP Open Cloud what-changed. Stop: Stop Granting Without Permissions. Hub: Roblox Studio guide. Roadmap: Fall lock. Cross-engine: Unreal MCP Stop. Analytics kit (different problem): Journey event checks. Help: HTTP 403. Resources: 25 Discords. Courses: /courses.
Key takeaways
- Twelve free checks before wiring agents to Studio MCP Open Cloud.
- Checks 1–4 are the wire gate; 5–12 earn production claims.
- Full access without a ticket fails check 2.
- Money and Publish assets default off (check 3).
- External MCP ≠ Studio Assistant (check 4).
- Look-only dry-run before writes (check 5).
- Collaborators set their own scopes (check 6).
- Skills teach; humans still grant (check 7).
- Minimize upload folders (check 8).
- Confirm imports; uploads are permanent (check 9).
- Save/Publish before HTTP allow-list (check 10).
- Revoke elevated scopes same day (check 11).
- CapEx + screenshot close the kit (check 12).
- Quotable: wire only when the twelve-check scorecard is green.
- Re-read Creator docs when sections expand.
FAQ
What are roblox mcp open cloud checks?
A free twelve-item preflight before connecting an external MCP client that can call Open Cloud via Studio after November 4, 2026.
Do I need all twelve before first connect?
Run 1–4 before wire. Complete 5–12 before claiming production-ready or enabling Money/Publish.
Official docs?
Use Open Cloud with the Studio MCP server and the DevForum announcement.
Why mention the Weekly Recap?
It documents that unsaved places cannot add HTTP allow-list domains — check 10.
Is this the Stop article?
No. Refusal language: Stop Granting Without Permissions. This is the scorecard.
Where is the capability map?
What Roblox Studio MCP Open Cloud Access Changed for Creators - 2026
Are these checks free?
Yes — Studio Permissions tab, Creator docs, and Discord paste only. No paid SaaS required.
What if Full access is required for a demo?
Treat it as a ticketed temporary Custom/Full window, then revoke (checks 2 and 11). Prefer non-prod.
Do collaborators inherit my pass?
No. Check 6 fails if you assume inheritance.
How does this differ from Journey event checks?
Journey checks cover Analytics Journeys. This kit covers MCP Open Cloud agent wiring.
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)