MultiConnect CLI
One command from your build to a live deployment.
The CLI builds, uploads and rolls out your server, API or website. A new build starts next to the current one and takes traffic only once it is healthy. The same command works in CI.
$ multiconnect deployPacking the buildUploadingStarting the new buildHealth check passedTraffic moved to new buildOld build kept for rollbackLive$
Containers
Traffic
Quick start
Three commands
Runs on Windows, macOS and Linux. Needs the .NET 10 SDK or later, even for projects that do not use .NET.
# Install dotnet tool install --global MultiConnect.CLI # Once per project folder: link it to a deployment multiconnect init # Every release after that multiconnect deploy
dotnet tool update --global MultiConnect.CLI
What it does
Everything a release needs, from the terminal
One command to deploy
Runs your build command, packages the output, uploads it and rolls it out, then waits until it is live.
The current build keeps serving
Until every new container is healthy. If the new build never becomes healthy, the previous one is restored.
Players stay connected
For game servers with a grace period, old servers keep running so connected players are not dropped.
Change settings as you deploy
deploy --config updates environment variables, start command, container counts, autoscaling and on-demand limits together with the build.
Status, logs and cost
State, build version, connection details, live logs, usage, cost per hour and your balance.
Keep, roll back and retire server builds
See which game server builds are running, bring a kept build back as the latest, or retire one.
A game's backend too
Players, remote config, leaderboards, economy, inbox, push and in-app products, without opening the dashboard.
Works with your AI assistant
A skill for Claude, Cursor, Copilot and others. It asks before every command and never sees your key.
Made for CI
No prompts in CI, clear exit codes, and keys read from pipeline secrets.
Reference
Commands
| Command | What it does |
|---|---|
multiconnect init | Choose which deployment this folder is for and how to build it. Saves multiconnect.json |
multiconnect deploy | Build, package, upload and roll out, then wait until live |
multiconnect deploy --config | The same, but change settings first; settings and build go live together |
multiconnect status | State, build version, any rollout in progress, and the containers |
multiconnect logs | The latest output of one container. --follow keeps printing, --filter shows only matching lines, --lines sets how many |
multiconnect info | Connection details |
multiconnect balance | Balance, spend per hour and how long the balance will last |
multiconnect analytics | Cost per hour, usage against the plan, and CPU, memory and storage per container |
multiconnect versions | Server deployments: the builds running now, whether latest, kept or draining |
multiconnect versions promote <build> | Makes a kept server build the latest again, which is how you roll back |
multiconnect versions retire <build> | Stops a kept build taking new players; its containers go after the grace period |
For games
Run a game's app backend from the terminal
The same things the dashboard's SDK app pages do, for scripts, pipelines and AI assistants. Name the game on each command. Commands that reach players, such as a gift or a push, say so before they run.
| Commands | What they cover |
|---|---|
multiconnect app overview, app usage, app stores | The backend at a glance, daily usage and store connections |
multiconnect app players list / show / activity / wallet | Find a player; see sign-ins, save and scores, devices, events and errors, wallet and ledger |
multiconnect app config show / set / publish / rollback / gate | Remote config, the version gate and maintenance |
multiconnect app boards list / entries / save / reset | Leaderboards and their entries |
multiconnect app economy … and app rewards … | Currencies, coin store, ad reward, daily bonus and tasks |
multiconnect app inbox send / list / delete | A message or gift to one player or to every player |
multiconnect app push send / show / cancel | A push notification now or at a set time |
multiconnect app errors list / show / status | Error groups; resolve, ignore or reopen one |
multiconnect products pull / push / plan / sync | The in-app product list as a JSON file in your repo, and its sync to Google Play and the App Store |
Unity
Works with Build and Deploy Server
The Unity editor window and the CLI share multiconnect.json, so a project linked by either one works in both. Build in Unity, then deploy the same build from a terminal or from CI.
# After building once in Unity
multiconnect deploy --skip-buildSecurity
Deploy keys, not your password
The CLI signs in with an access key that has "Allow deploys (CLI)" turned on. Create the key in the dashboard and attach it to the deployments it may deploy.
- A deploy key reaches only the deployments it is attached to.
- It can upload builds, redeploy and read status, connection details, usage and balance.
- It cannot create, delete or stop deployments, or change plans. Those stay in the dashboard.
- Every request is signed with HMAC-SHA256, body included, so a captured request cannot be altered or replayed.
- Deploys made with the CLI appear in the account activity log, with the key that made them.
CI
Deploy from GitHub Actions
Commit multiconnect.json, store the key and secret as pipeline secrets, and run deploy. The same works in GitLab CI or any other pipeline.
- uses: actions/setup-dotnet@v4
with: { dotnet-version: '10.0.x' }
- run: dotnet tool install --global MultiConnect.CLI
- run: multiconnect deploy --tag ${{ github.sha }}
env:
MC_ACCESS_KEY: ${{ secrets.MC_ACCESS_KEY }}
MC_ACCESS_SECRET: ${{ secrets.MC_ACCESS_SECRET }}AI assistants
Let your coding assistant deploy for you
The MultiConnect skill teaches an assistant to use the CLI: deploy a build, check status, usage and cost, read your balance and run a game's app backend. The AI Agent Guide goes further and explains the SDK and the platform, so the assistant can build your game with them too. Both tell it to ask before every command, including read-only ones, and never to ask for your key.
Claude Code
Unzip the skill to ~/.claude/skills/multiconnect-cli/ for every project, or .claude/skills/multiconnect-cli/ inside one.
Claude apps
Add a custom skill in Claude's settings and upload the .zip.
Cursor, Copilot and others
Add the contents of SKILL.md as project rules or custom instructions.
Questions about the CLI
Can the CLI create a new deployment?
No. Create the deployment once in the dashboard, attach a deploy key, and use the CLI for every release after that.
Is it safe to commit multiconnect.json?
Yes. It holds the linked deployment and your build settings. The key inside it is encrypted for the machine and user that ran init, so a committed copy is useless anywhere else. In CI the key comes from pipeline secrets.
What happens if a deploy fails?
The current build keeps serving. If the new containers never become healthy, the previous build is restored and the CLI exits with a non-zero code.
Can I use one key for several deployments?
Yes. A key can be attached to several deployments, and each project folder is linked to exactly one of them.
Can it show my logs?
Yes. multiconnect logs prints the latest output of a container, and --follow keeps printing new lines.
Can I roll a game server back?
Yes, if the redeploy kept the previous build. multiconnect versions lists the builds and multiconnect versions promote makes a kept one the latest again.
Does it work for databases?
Databases have no build, so deploy does not apply. status, info, balance and analytics all work.
Does an AI assistant see my access key?
No. You link the folder yourself with multiconnect init and the key is stored encrypted on your machine. The skill tells the assistant never to ask for it, never to put it on a command line and never to print it.
Try it with 500 free credits
Create an account and you get 500 credits to deploy with. No credit card required. There is no free hosting tier; the credits are the trial.