Skip to main content
The deploy command handles both deploying add-ons to Minecraft installation directories for testing and exporting projects as packaged files (.mcpack, .mcaddon) for distribution.

​
Syntax

mct deploy <mode> [options]

​
Arguments

​
mode
string
required
Destination for deployment.Choices:
  • mcuwp - Minecraft Bedrock Edition (Retail)
  • mcpreview - Minecraft Preview
  • server - Dedicated server path
  • folder or output - Custom output folder
  • [custom-path] - Any custom directory path

​
Options

​
-i, --input-folder
string
Path to the add-on project folder to deploy.
​
-if, --input-file
string
Path to a packaged file (MCPack, MCAddon) to deploy.
​
-o, --output-folder
string
Custom output folder when using folder mode.
​
-f, --force
boolean
Force overwrite of existing files.

​
Examples

​
Deploy to Minecraft Bedrock

mct deploy mcuwp -i ./my-addon
Deploys your add-on to the Minecraft Bedrock Edition installation. The add-on will appear in:
  • Behavior Packs folder
  • Resource Packs folder
Windows:
C:\Users\[username]\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\
├── behavior_packs\your-addon\
└── resource_packs\your-addon\
Android:
/storage/emulated/0/games/com.mojang/
├── behavior_packs/your-addon/
└── resource_packs/your-addon/

​
Deploy to Minecraft Preview

mct deploy mcpreview -i ./my-addon
Deploys to the Minecraft Preview installation for testing beta features.

​
Deploy to custom folder

mct deploy folder -i ./my-addon -o ./test-deployment
Deploys to a custom location, useful for:
  • Manual testing
  • Creating distribution packages
  • Sharing with team members

​
Deploy to dedicated server

mct deploy server -i ./my-addon
Deploys to the configured dedicated server path.

​
Force deployment (overwrite)

mct deploy mcuwp -i ./my-addon -f
Forces overwrite of existing files without prompting.

​
Deploy packaged file

mct deploy mcuwp -if ./packages/my-addon.mcaddon
Deploys directly from a packaged .mcaddon or .mcpack file.

​
Deployment Modes

Deploys to the main Minecraft Bedrock Edition installation.Default Paths:
  • Windows: %localappdata%\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\
  • iOS: /var/mobile/Containers/Data/Application/[UUID]/games/com.mojang/
  • Android: /storage/emulated/0/games/com.mojang/
Use Case: Testing in the stable release version

​
What Gets Deployed

The deploy command copies: 
behavior_packs/
└── your-addon/
    ├── manifest.json
    ├── pack_icon.png
    ├── scripts/
    ├── entities/
    ├── items/
    ├── blocks/
    └── [all BP files]

​
After Deployment

​
In Minecraft Bedrock/Preview

  1. Launch Minecraft
  2. Create a new world or edit an existing world
  3. Go to Add-Ons or Resource Packs
  4. Your add-on appears in the available packs
  5. Activate it and start playing

​
Verification

After deploying, verify the files: Windows: 
# Check if deployed successfully
dir "%localappdata%\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\behavior_packs"
Linux/Mac: 
# If using Android via ADB
adb shell ls /storage/emulated/0/games/com.mojang/behavior_packs

​
Workflow Integration

Combine deploy with other commands for a complete development workflow:

​
Edit → Validate → Deploy

# 1. Make changes to your addon
# 2. Validate
mct validate -i ./my-addon -show

# 3. If validation passes, deploy
mct deploy mcpreview -i ./my-addon -f

# 4. Test in Minecraft Preview

​
Automated Deployment Script

deploy.sh (Linux/Mac): 
#!/bin/bash
echo "Validating addon..."
mct validate -i ./my-addon -show

if [ $? -eq 0 ]; then
  echo "Validation passed. Deploying..."
  mct deploy mcpreview -i ./my-addon -f
  echo "Deployed to Minecraft Preview"
else
  echo "Validation failed. Fix errors before deploying."
  exit 1
fi
deploy.bat (Windows): 
@echo off
echo Validating addon...
mct validate -i ./my-addon -show

if %errorlevel% equ 0 (
  echo Validation passed. Deploying...
  mct deploy mcpreview -i ./my-addon -f
  echo Deployed to Minecraft Preview
) else (
  echo Validation failed. Fix errors before deploying.
  exit /b 1
)

​
World Settings

Combine deployment with world configuration: 
# Deploy addon
mct deploy mcpreview -i ./my-addon

# Configure world settings
mct world set -i ./my-addon --beta-apis --editor
This deploys your addon and ensures the test world has:
  • Beta APIs enabled
  • Editor mode active

​
Server Deployment

For dedicated servers:

​
Configure Server Path

Set the server path in your environment: 
mct version  # Shows current paths
The server path is typically:
  • Windows: C:\Users\[user]\AppData\Local\minecraft-creator-tools\servers\
  • Linux: ~/.minecraft-creator-tools/servers/

​
Deploy to Server

mct deploy server -i ./my-addon -f

​
Server Directory Structure

After deployment: 
server-directory/
├── behavior_packs/
│   └── your-addon/
├── resource_packs/
│   └── your-addon/
├── worlds/
│   └── Bedrock level/
├── server.properties
└── bedrock_server.exe

​
Troubleshooting

The CLI cannot locate the Minecraft installation path.Solution: Check installation paths:
mct version
If paths are incorrect, Minecraft may not be installed or is in a non-standard location. Use custom path deployment:
mct deploy /path/to/minecraft/com.mojang -i ./my-addon
Cannot write to Minecraft directory.Solution:
  • Close Minecraft before deploying
  • Run command prompt as Administrator (Windows)
  • Check folder permissions
# Windows (run as Administrator)
mct deploy mcuwp -i ./my-addon -f
Files deployed but not visible in game.Solution:
  1. Verify deployment location: 
    mct version  # Check paths
  2. Check manifest.json format
  3. Ensure UUIDs are unique
  4. Restart Minecraft completely
  5. Validate the addon: 
    mct validate -i ./my-addon -show
Minecraft is caching the previous version.Solution:
  1. Force deployment: 
    mct deploy mcpreview -i ./my-addon -f
  2. Clear Minecraft cache:
    • Close Minecraft completely
    • Delete the specific addon folder
    • Redeploy

​
Advanced Usage

​
Deploy Multiple Projects

mct deploy mcpreview -i ./addon1 -f
mct deploy mcpreview -i ./addon2 -f
mct deploy mcpreview -i ./addon3 -f

​
Deploy to Multiple Targets

# Deploy to both retail and preview
mct deploy mcuwp -i ./my-addon -f
mct deploy mcpreview -i ./my-addon -f

​
Deploy with World Settings

Combine deployment with world configuration: 
# Deploy
mct deploy mcpreview -i ./my-addon -f

# Update world settings
mct world set -i ./my-addon -beta-apis -editor

​
Custom Deployment Path

Deploy to any location: 
mct deploy /custom/minecraft/path -i ./my-addon

​
Best Practices

Development Workflow:
  1. Validate before deploying: mct validate -i ./addon -show
  2. Deploy to Preview for testing beta features
  3. Use -f flag for rapid iteration
  4. Test in Retail before release
  5. Keep backups of working versions
Version Control:
  • Use git to track addon changes
  • Tag releases before deploying
  • Test deployments in Preview first
Testing:
  • Deploy to Preview for experimental features
  • Test multiplayer in dedicated server
  • Validate on different platforms before release

Build docs developers (and LLMs) love

Get started for freeTalk to us