symbionix-sl/airstrings-cli

CLI and MCP server for AirStrings: over-the-air string updates for iOS, Android, web and React Native apps, and Go backends.
Manage strings and locales from the terminal or let an AI agent do it over MCP. airstrings publish has AirStrings sign the bundle (Ed25519) and push it to the CDN; the SDKs verify the signature before showing anything.
Listed in the MCP Registry as io.github.symbionix-sl/airstrings-cli.
## Install
bash
npm install -g @airstrings/cli # any platform, Node 18+
brew install symbionix-sl/airstrings/airstrings # macOS / Linux
go install github.com/symbionix-sl/airstrings-cli/cmd/airstrings@latest # Go 1.26.1+
Installs airstrings and airstrings-mcp.
## Quick start
bash
cd my-project
airstrings init # log in, create a project, bind this folder
airstrings strings set welcome.title en="Hello" es="Hola" --format text
airstrings push # send local strings to staging
airstrings publish # sign + publish staging bundles
airstrings sdk-config # IDs, public key and SDK snippets for production
With no key, init opens the browser to log in (an owner of your organization approves), stores an org key in ~/.config/airstrings/credentials.json, creates a project named after the folder and writes .airstrings/config.json. --name names the project, --project binds an existing one, airstrings init binds to the key's project. Without a terminal it waits up to 90 s for approval; on timeout, --no-browser or CI it exits 9 with the URL: approve, then re-run the same command.
Staging is active after init. Production is protected: it rejects direct writes and publishing, and changes reach it only by promotion, applied by a human in the dashboard or by airstrings promote --to production with a full-power org key.
## Keys
| Key | Prefix | Covers | Get it |
| Org key | asorg | every project of the org | airstrings login |
| Project key | asproj | every environment of one project | dashboard → API keys |
| Legacy environment key | 64 hex | one environment | created before 0.18 |
Precedence: AIRSTRINGSORGAPIKEY > AIRSTRINGSAPIKEY > workspace key > stored login. In CI use a project key in AIRSTRINGSAPIKEY; across several projects use a gated (non-full-power) org key from the dashboard in AIRSTRINGSORGAPIKEY. No init needed when one of these is set.
## Commands
bash
# Account and context
airstrings login | logout # store / revoke the org key
airstrings org # stored logins; org use switches
airstrings status # project, env, key scope, protection + next step
airstrings project # current project; project ls lists the org's
airstrings --project # run against another project (org key)
# Environments
airstrings env # environments: protected/open, key stored or not
airstrings env use staging # switch (shorthand: airstrings -e -u staging)
airstrings env rm # remove environment credentials
airstrings locales # locales with string counts
airstrings sdk-config [--env ] # IDs + public keys + SDK snippets (default production)
# API keys
airstrings apikey ls # the project's keys (✓ = stored in this workspace)
airstrings apikey rotate # rotate the workspace key
airstrings apikey revoke # revoke the workspace's stored keys (e.g. after a leak)