8. Check on a deployment
These change nothing, and you can run them any time.
| Command | Shows |
|---|---|
multiconnect status |
State, build version, any rollout in progress, and containers with their health |
multiconnect info |
Connection details: hostnames and ports |
multiconnect analytics |
Cost per hour, usage against the plan, and CPU, RAM and storage per container |
multiconnect balance |
Your credits, what the account spends per hour, and how long the balance lasts |
multiconnect logs |
The latest output of one container |
multiconnect versions |
Server deployments: the builds running now — the latest, kept and draining |
Read the logs
multiconnect logs
multiconnect logs --container my-api-1 --lines 500
multiconnect logs --follow --filter error
--follow (-f) keeps printing new lines until you press Ctrl+C. --filter prints only the lines that contain the text. Without --container, the first running container is shown; multiconnect status lists the names.
Server builds: keep, roll back, retire
A server redeploy can keep the current build running for game clients built for it. multiconnect versions lists those builds. Two commands act on a kept build, and both ask before they run (add --yes in CI):
| Command | What it does |
|---|---|
multiconnect versions promote 1.0.0.8 |
Makes kept build 1.0.0.8 the latest again, deployed as a new build number. The current latest drains after the grace period, or add --keep-days 7 or --keep-until-retired to keep it for clients built for it |
multiconnect versions retire 1.0.0.8 |
Stops kept build 1.0.0.8 taking new players; its containers are removed after the grace period |
In-app products
An SDK app's in-app products are one list on the dashboard's Store Products page. MultiConnectCloud creates them and keeps them in step in Google Play and the App Store. The products commands work with that list from your repo or CI.
Name the app with --sdk-key mck-…, or set MC_SDK_KEY. The deploy key in this folder's credentials authorises the call, and the app must belong to the same account.
| Command | What it does |
|---|---|
multiconnect products pull |
Writes the list to store-products.json (or --file) |
multiconnect products push |
Writes the file into the list. Add --remove-missing to remove products the file leaves out. Nothing reaches a store yet |
multiconnect products plan |
Shows what a sync would change in each store. Exits with 2 when a product changed in more than one place; choose which value to keep on the dashboard |
multiconnect products sync |
Applies the plan and waits for the result |
multiconnect products copy |
Copies the product list from another of your apps into this one |
multiconnect products screenshot <image> --product <key> |
Sets the App Store review screenshot for a product. Repeat --product for several, or use --missing for every product that has none. It is sent to Apple with the next sync |
sync asks before it creates or deactivates a store product, because store product ids can never be changed or reused. In CI, add --yes. App Store products stop at Ready to Submit; submit them in App Store Connect.
An SDK app's backend
Everything on an SDK app's pages on the dashboard can also be done from a terminal, a pipeline or an AI assistant: look up a player, read errors, change remote config, send a gift or a push notification. The SDK Apps Guide explains each feature; this section lists the commands.
Set up once per machine. These commands need an access key with Allow deploys (CLI) turned on. No deployment has to be attached to it. Then run:
multiconnect sdk-init --sdk-key mck-your-key
It stores the key for this machine and makes that app the default. A folder already linked with multiconnect init works too. In CI, set MC_ACCESS_KEY, MC_ACCESS_SECRET and MC_SDK_KEY instead. multiconnect sdk-init --forget removes the stored key.
Name the app on each command when the account has more than one. Put its name first, with a dash and no spaces, or use --game or --sdk-key:
multiconnect -Carrom app overview
multiconnect --game "8 Ball Pool" app players list --search priya
Add --json to any command to get the result as JSON.
Commands that only read:
| Command | Shows |
|---|---|
app overview, app usage, app stores |
The app at a glance, daily usage, and its store connections |
app players list --search <text> |
Players found by name, email, player id or your game's own id |
app players show <player-id> |
Sign-in methods, save and scores |
app players activity <player-id> |
Devices, analytics events and errors, newest first. --kind events or --kind errors narrows it, --event <name> picks one event, --cursor <next> reads the next page |
app players wallet <player-id> |
Wallet and ledger |
app config show, app config versions |
Remote config and its published versions |
app boards list, app boards entries |
Leaderboards and their entries |
app economy show, app rewards show |
Currencies, coin store, ad reward, daily bonus and tasks |
app inbox list, app push show |
Messages sent, and push notifications sent or scheduled |
app errors list, app errors show <error-id> |
Error groups, and one group in full |
Commands that change something. Each of these asks before it runs. In CI, add --yes.
| Command | What it changes |
|---|---|
app config set, publish, rollback, gate, delete |
Remote config, for every player. publish makes the draft live. gate sets the minimum version and maintenance, and can stop players from playing |
app boards save, delete, reset |
Leaderboards. delete and reset remove scores for good |
app economy ...-save, ...-delete, ad-reward |
Currencies, coin store items and the ad reward |
app rewards ...-save, task-delete, tasks-per-day |
The daily bonus, daily tasks and level multipliers |
app inbox send |
Sends a message or a gift. Without --player it goes to every player |
app inbox delete |
Removes a message from every inbox |
app push send |
Sends a push notification, now or at --send-at. Without --player it goes to every player |
app push cancel |
Cancels a scheduled push |
app errors status <error-id> --status 2 |
Marks an error group resolved (2), ignored (3) or open again (1) |
Send a gift or a push:
multiconnect -Carrom app inbox send --title "Sorry about the crash" --body "Here are 500 coins." --gift '{"currencies":{"coins":500}}' --player 81f3
multiconnect -Carrom app push send --title "Weekend event" --body "Double coins until Sunday." --send-at 2026-12-05T12:00:00Z
- Repeat
--playerto send to several players. - Times are UTC.
- The gift is a grant, in the same JSON form the SDK Apps Guide describes.
Change an existing entry by reading it with --json, editing that JSON, and sending it back with --data '{...}' or --data-file, including its id. Leave the id out to create a new entry.
If your game keeps its own inbox, messages and gifts go to your game API, as the SDK Apps Guide describes. The gift then uses your game's own currency names.

