AutoBlox MCP server

AutoBlox

A cross-agent, local-first production toolkit for building original Roblox games with AI.

One master skill · 41 original Roblox-focused playbooks · Guided design meetings · Blender + Roblox Studio MCP onboarding · Real release gates

Get started · Download · Copy-paste prompts · Setup guide · Contributing

---

Make a game worth finishing

AutoBlox gives your AI coding assistant a repeatable way to meet with you about a game concept, challenge and refine the idea, turn decisions into an approved specification, then implement, test and prepare a private Roblox release candidate. The workflow is inspired by production lessons from a real Roblox development project, but the distributed toolkit does not contain that game's source, characters, private place identifiers or assets.

It is built for people making their first Roblox game and creators building multiple different games. It favors small, enjoyable, complete experiences before expansions; clear project ownership; reusable Blender assets; server-authoritative Luau; and evidence instead of “it should work.”

Preview status: AutoBlox is a development framework, not a one-click game generator. Offline tests pass, but real Codex/Claude/Studio/Blender MCP connections and fully autonomous end-to-end game production have not yet been independently certified. An AI agent requires its own tool access, permissions, time and successful runtime tests. Public Roblox release always requires the creator's approval.

What you get

Capability	What AutoBlox does
🧠 Design council	Guides a practical idea-to-final-directive meeting; defines audience, core loop, controls, art, scope and acceptance criteria
🏗️ Production supervisor	Tracks tasks, prerequisites, agent responsibilities, evidence, recoverable milestones and current project state
🎮 Roblox engineering	Routes to Luau, characters, networking, persistence, UI, physics, input, camera and security practices
🎨 Blender-first assets	Encourages editable, optimized original models and animations; validates real Studio integration
🤝 Cross-agent	Codex, Claude Code, Cursor, Gemini CLI, GitHub Copilot/VS Code; generic skill/MCP fallback
🔌 First-run setup	Checks for Roblox Studio and Blender, offers installation and optional MCP connections, and calls for real tool verification
✅ Evidence-gated release	Distinguishes source checks, Studio multiplayer tests, device evidence and a saved private build
🔒 Safe by default	No silent installs, hooks, publication, purchases, force pushes or credential storage

Download

Recommended: Complete AutoBlox Toolkit (ZIP)

Existing projects: Master Skill Only (ZIP)

Release notes & checksums · Browse source code · All releases

Available now: Both ZIPs and the SHA-256 checksum file are published in the v0.3.0-preview release. This is a preview toolkit: live end-to-end production across all agents is not yet certified.

Quick start

Requirements: Python 3.9+, Git (optional but recommended), and a supported AI coding agent. Roblox Studio is available for Windows and macOS; Blender is available for Windows/macOS/Linux. The first-run setup offers missing tools and checks MCP availability; it does not secretly install software.

1. Clone the toolkit:

git clone https://github.com/reallyzip/autoblox.git
cd autoblox

Or download and extract the complete toolkit ZIP from Releases.

2. Scaffold a fresh Roblox game:

python3 scripts/new_game.py \
  --name "My First Roblox Game" \
  --genre "Co-op adventure" \
  --dest ../my-first-roblox-game \
  --git-init
cd ../my-first-roblox-game

On Windows PowerShell, use one line and replace python3 with py:

py scripts/new_game.py --name "My First Roblox Game" --genre "Co-op adventure" --dest ../my-first-roblox-game --git-init

Run the PowerShell example from the downloaded AutoBlox toolkit directory, then change into ../my-first-roblox-game.

3. Inspect the environment (safe, read-only):

python3 scripts/setup_environment.py --project . --agent auto

4. Offer setup only with consent:

python3 scripts/setup_environment.py --project . --agent codex --interactive
# or --agent claude / cursor / gemini / vscode / copilot / other

For the actual MCP connection, enable Studio's built-in server and approve the optional Blender community bridge. Your agent must perform read-only live calls to both apps; merely adding config does not prove connectivity. Full walkthrough.

5. Open your new game's folder in your AI coding tool, then paste:

Use the roblox-studio-architect skill in this project. First inspect the current
project and check whether Roblox Studio and Blender are installed and connected
to this agent through MCP. Offer safe installation/setup if either is missing;
ask before changes and verify live read-only tool calls. Then run a professional
game design meeting with me, challenge scope, agree on a final game directive,
and wait for my approval before implementation. After approval, create one
polished playable slice first, then develop and independently verify the full
approved game. Keep my Roblox experience PRIVATE until I explicitly authorize
public release; show actual tests, Git checkpoints and remaining blockers.

This prompts the local installed skill. Pasting it alone into an agent without the toolkit does not install the skill.

Copy-paste into your AI agent

For a new project created by new_game.py, the skill and client instructions are already in the game folder. Choose a launch prompt:

Use $roblox-studio-architect in this repository. Run first-use environment and
MCP checks, then guide me through the AutoBlox design council for a new Roblox
game. Once I approve the final directive, coordinate development using the
project's playbooks, Blender, Luau, Rojo, and Roblox Studio. Verify with real
Studio tests before reporting a private release candidate. Do not publish or
spend money without asking.

Codex setup

Read CLAUDE.md and the roblox-studio-architect skill provided in this project.
Use AutoBlox to check my Roblox Studio and Blender setup, offer safe MCP
onboarding, and verify the actual tools before making in-Studio claims. Lead a
full game concept meeting and obtain my approval of one final directive. Then
implement an original Roblox game with small verified milestones, real tests,
Blender asset provenance and a private release-candidate handoff.

Claude Code setup

Read the project .cursor rules, AGENTS.md and the canonical
.agents/skills/roblox-studio-architect/SKILL.md. Follow the AutoBlox design,
implementation and test workflow. First check Roblox Studio and Blender MCP
connections; offer missing setup with my consent, then run a design meeting.
Do not begin full production until I approve the final game directive.

Cursor setup

Read GEMINI.md, AGENTS.md and the AutoBlox master skill in .agents/skills.
Start with environment and MCP checks, then a professional Roblox game design
meeting. Ask me to approve the complete directive before building. Develop
using verified milestones, real multiplayer tests and private release gates.

Gemini CLI setup

Use .github/copilot-instructions.md, AGENTS.md, and
.agents/skills/roblox-studio-architect/SKILL.md to follow AutoBlox. Begin by
offering Roblox Studio and Blender setup, verify MCP tool connectivity from
this agent, and run a final-directive design meeting. After approval, develop
and test the game with evidence-gated private release preparation.

Copilot/VS Code setup

Using another agent? Open AGENTS.md and the canonical SKILL.md; follow the generic adapter. The skill relies on ordinary files and does not assume every vendor supports automatic skill discovery or MCP.

How AutoBlox works

flowchart TD
    A[Start a new game] --> B[Detect tools and MCP]
    B --> C[Design council meeting]
    C --> D{Creator approves final directive?}
    D -->|Revise| C
    D -->|Yes| E[Build polished vertical slice]
    E --> F[Implement approved milestones]
    F --> G[Independent review and Studio tests]
    G --> H{Release blockers?}
    H -->|Yes| F
    H -->|No| I[Verified private release candidate]
    I --> J[Creator test drive and launch decision]

The master skill loads only the playbooks needed for the task. It does not stuff all 41 playbooks into every conversation, reinstall existing plugins, or claim nonexistent subagent/tool capabilities.

The 41 specialist playbooks

Original task-specific Roblox guidance inspired by the categories in Awesome Gamedev Agent Skills, Ponytail, Superpowers, Caveman and established software-engineering practice. These are independently authored workflows, not copied or bundled upstream skills. Consult playbook coverage and source acknowledgments.

Examples: Roblox networking and server authority, Luau, persistence, asset generation, Blender integration, avatars/animation, UI, controls, sound, physics, game feel, performance, TDD, root-cause debugging, agent delegation, security review, skill authoring, and concise evidence-led reporting.

Safety, scope and evidence

• Private by default. Public audience changes, monetization and final Roblox launch need explicit user approval.
• Nothing auto-installs. The environment wizard offers official installers and optional MCP setup; it requires consent before modifying configuration or running community code.
• Blender MCP is optional and potentially powerful. The community bridge may execute Python inside Blender; verify and trust the software before connecting it.
• No guaranteed autonomous launch. Real Studio access, correct asset permissions, testing and human acceptance remain necessary.
• Source-of-truth first. Preserve existing projects, saved player data, branches, and recoverable Git checkpoints.
• No affiliation. AutoBlox is independent, not affiliated with or endorsed by Roblox, OpenAI, Anthropic, Blender or the referenced skill projects.

Developers and contributors

• Installation and troubleshooting
• Agent adapters and copy-paste prompts
• Roblox Studio + Blender MCP setup
• Architecture and production stages
• FAQ
• Roadmap
• Launch, creator partnerships and discoverability plan
• Creator media kit · 30-day launch calendar · Community showcases
• Contributing · Security policy · Code of Conduct

Run offline checks before opening an issue or submitting a pull request:

python3 -m unittest discover -s scripts/tests -v
python3 scripts/verify_package.py
python3 scripts/build_release.py

MIT licensed. See LICENSE and third-party notices. Suggestions, bug reports, and pull requests are welcome. Open an issue.