MultiConnectSDK › CLI
13. Command reference
| Command | Changes anything? | What it does |
|---|---|---|
multiconnect init |
Writes multiconnect.json |
Links this folder to a deployment |
multiconnect deploy |
Yes, the live deployment | Builds, uploads and rolls out |
multiconnect deploy --config |
Yes, the live deployment | Changes settings, then deploys |
multiconnect status |
No | State, version and containers |
multiconnect info |
No | Connection details |
multiconnect analytics |
No | Cost, usage and container resources |
multiconnect balance |
No | Credits and spend |
multiconnect logs |
No | A container's latest output; --follow keeps printing |
multiconnect versions |
No | Server builds running now |
multiconnect versions promote |
Yes, the live deployment | Makes a kept server build the latest again |
multiconnect versions retire |
Yes, the live deployment | Retires a kept server build |
multiconnect products pull |
Writes a file | Saves the app's in-app product list as JSON |
multiconnect products push |
Yes, the product list | Writes a JSON file into the list |
multiconnect products plan |
No | What a store sync would change |
multiconnect products sync |
Yes, Google Play and the App Store | Creates and updates the products in both stores |
multiconnect products copy |
Yes, the product list | Copies another app's product list into this one |
multiconnect products screenshot |
Yes, sent with the next sync | Sets App Store review screenshots |
multiconnect sdk-init |
Stores a key on this machine | Sets the machine up for the app commands |
multiconnect app ... (read commands) |
No | An SDK app's players, config, leaderboards, economy, inbox, push and errors |
multiconnect app ... (change commands) |
Yes, the live app and its players | Changes config, boards, economy and rewards; sends messages, gifts and pushes |
multiconnect init options:
| Option | What it does |
|---|---|
--deployment |
The deployment's name or id, when the key has several |
--build-path, --build-command |
The build answers from Section 4 |
--worker-build-path, --worker-build-command |
The same for the game server build |
--force |
Replaces an existing multiconnect.json without asking |
To skip the questions for your key, set MC_ACCESS_KEY and MC_ACCESS_SECRET first. --key gives the key on the command line; the secret is never taken from the command line, where it would end up in your shell history. With --key, the secret comes from MC_ACCESS_SECRET, or you are asked for it.
For any command's full options, add --help.

