Skip to main content
The create command scaffolds a new Minecraft add-on project from a gallery template with proper structure, manifests, and starter content.

​
Syntax

mct create [name] [template] [creator] [description]

​
Arguments

All arguments are optional. If not provided, you’ll be prompted interactively.
​
name
string
The short name for your project (no spaces, under 20 characters).Example: my-addon, cool-blocks
​
template
string
Template ID from the gallery to use as a starting point.Common templates:
  • starter - Basic add-on with behavior and resource packs
  • blocks - Block-focused template
  • entities - Entity-focused template
  • items - Item-focused template
If not specified, you’ll be shown a list of available templates.
​
creator
string
Your creator name (appears in project metadata).Example: Creator, StudioName
​
description
string
Project description (appears in manifest).Example: “My awesome Minecraft add-on”

​
Options

​
-o, --output-folder
string
Destination folder for the new project. If not specified, creates a subfolder in the current directory.
​
-i, --input-folder
string
Working directory for project creation.

​
Examples

Simply run the command and answer the prompts: 
mct create

┌─────┐
│ ▄ ▄ │ Minecraft Creator Tools (preview)
│ ┏▀┓ │
└─────┘

? What's your preferred project title? My Cool Addon
? What's your preferred project description? An addon with cool features
? What's your creator name? MyStudio
? What's your preferred project short name? (<20 chars, no spaces) my-cool-addon
? What's your preferred folder name? my-cool-addon
? What template should we use? 
  ❯ starter: Basic Minecraft Add-on
    blocks: Block-focused Add-on
    entities: Entity-focused Add-on
    items: Item-focused Add-on

​
Create with all arguments

mct create my-addon starter MyStudio "My awesome addon"
This creates a new project without any prompts.

​
Create in specific folder

mct create -o ./projects/my-new-addon

​
Non-interactive creation

For CI/CD pipelines or scripts: 
mct create my-addon starter StudioName "Automated addon creation"

​
What Gets Created

After running create, you’ll have a complete project structure: 
my-addon/
├── behavior_packs/
│   └── mystudio-my-addon/
│       ├── manifest.json
│       ├── pack_icon.png
│       ├── scripts/
│       │   └── main.js
│       └── texts/
│           ├── en_US.lang
│           └── languages.json
├── resource_packs/
│   └── mystudio-my-addon/
│       ├── manifest.json
│       ├── pack_icon.png
│       └── texts/
│           ├── en_US.lang
│           └── languages.json
├── package.json
└── README.md

​
After Creation

Once your project is created, you’ll see: 
All done! Now run npm i in the /path/to/my-addon folder 
to install dependencies, if any, from npm.

​
Next Steps

  1. Install dependencies (if your template includes them): 
    cd my-addon
npm install
  2. Start editing your addon files in the behavior_packs and resource_packs folders.
  3. Validate your project: 
    mct validate -i . -show
  4. Deploy to Minecraft for testing: 
    mct deploy mcuwp -i .

​
Available Templates

Templates are pulled from the Minecraft Creator Tools gallery. Common templates include:

starter

Basic add-on with behavior and resource packs. Perfect for beginners.

blocks

Includes examples of custom blocks with different properties.

entities

Template with custom entity examples and behaviors.

items

Custom item templates with various item types.
The exact list of available templates depends on the gallery configuration. Run mct create without arguments to see the current template list.

​
Project Naming Conventions

The CLI automatically generates proper project identifiers: Input:
  • Creator: MyStudio
  • Name: cool-addon
Generated:
  • Pack folder: mystudio-cool-addon
  • Manifest IDs: Auto-generated UUIDs
  • Display name: From title parameter

​
EULA Agreement

The first time you create a project, you’ll be prompted to agree to the Minecraft EULA: 
This feature uses Minecraft assets and/or the Minecraft Bedrock 
Dedicated Server. To use it, you must agree to the Minecraft End 
User License Agreement and Privacy Statement.

    Minecraft End User License Agreement: https://minecraft.net/eula
    Minecraft Privacy Statement: https://go.microsoft.com/fwlink/?LinkId=521839

? I agree to the Minecraft End User License Agreement and Privacy Statement (y/N)
Your agreement is saved and you won’t be prompted again.

​
Template Sources

Templates are synchronized from GitHub repositories. The CLI:
  1. Loads the template gallery
  2. Downloads the selected template from GitHub
  3. Processes and customizes it with your project details
  4. Generates unique UUIDs for manifests
  5. Applies your title, description, and creator name

​
Customization After Creation

You can modify project properties after creation using the mct set command: 
mct set title "New Title" -i ./my-addon
mct set description "New description" -i ./my-addon
mct set bpuuid "new-uuid" -i ./my-addon

​
Troubleshooting

The CLI checks if behavior/resource pack folders exist to prevent overwriting.Solution: Choose a different output folder or delete the existing project.
mct create -o ./projects/my-addon-v2
Templates are fetched from GitHub. Ensure you have internet connectivity.Solution: Check your internet connection and firewall settings.
Project names must be under 20 characters with no spaces.Solution: Use hyphens or underscores:
# Good
mct create my-cool-addon

# Bad
mct create "My Cool Addon With A Really Long Name"

​
Advanced Usage

​
Creating Multiple Projects

Create several projects in one session by running the command multiple times: 
mct create addon1 starter Studio "First addon"
mct create addon2 blocks Studio "Block addon"
mct create addon3 entities Studio "Entity addon"

​
Custom Output Structure

Control where projects are created: 
# Create in current directory
mct create my-addon

# Create in specific location
mct create -o /path/to/projects/my-addon

# Create multiple in organized structure
mct create -o ./workspace/addons/addon1
mct create -o ./workspace/addons/addon2

Build docs developers (and LLMs) love

Get started for freeTalk to us