AirStrings MCP server

airstrings

Command-line interface for AirStrings — manage strings, locales, bundles, and publishing from the terminal.

Install

npm (any platform)

npm install -g @airstrings/cli
airstrings <command>

Requires Node 18+. Installs airstrings and airstrings-mcp.

Homebrew (macOS / Linux)

brew install symbionix-sl/airstrings/airstrings

From source

go install github.com/symbionix-sl/airstrings-cli/cmd/airstrings@latest

Build locally

git clone git@github.com:symbionix-sl/airstrings-cli.git
cd airstrings-cli
go build -o airstrings ./cmd/airstrings

Setup

Initialize a workspace in your project directory:

cd my-project
airstrings init ask_live_xxxxxxxxxxxx

This validates the key, auto-detects your project and environments, and stores everything in .airstrings/config.json. Each project has its own workspace — no shared global config.

Environments

airstrings env                      # list environments (✓ = active)
airstrings env use staging          # switch to staging
airstrings env add <api-key>        # add credentials for another environment
airstrings env rm staging           # remove environment credentials
airstrings -e -u staging            # shorthand for env use
airstrings status                   # show current project, env, and key

Usage

airstrings <command> [options]

Project & Environments

airstrings project                  # Show project info
airstrings env                      # List environments
airstrings env use staging          # Switch active environment
airstrings env create staging       # Create a new environment
airstrings locales                  # List locales with string counts

Strings

strings set and strings rm are local-first: they edit the workspace CSVs and never call the API unless --push is given.

airstrings strings list                          # List all strings (remote)
airstrings strings list --locale en --limit 50   # Filter by locale
airstrings strings ls --local                    # List local workspace strings (offline, no credentials)
airstrings strings ls --local --section onboarding   # List one section, offline
airstrings strings get welcome.title             # Get a single string (remote)
airstrings strings set welcome.title en="Hello" es="Hola" --format text   # Write to local CSVs
airstrings strings set app.name en="My App" --format text --push     # Also upsert to the API
airstrings strings rm old.unused.key             # Remove from local CSVs
airstrings strings rm old.unused.key --push      # Also delete from the API
airstrings strings rm welcome.title --locale es --push   # Remove one locale, locally and remotely

Sections

airstrings sections list
airstrings sections create onboarding --description "Onboarding flow strings"
airstrings sections delete sec_xxxxx

Bundles & Publishing

airstrings bundles                  # List published bundles
airstrings publish                  # Publish all locales
airstrings publish en es            # Publish specific locales

Offline-safe builds

Ship published bundles inside your app so SDKs can serve strings with no network — cold offline starts, SSG/SSR builds, CI:

airstrings bundles pull

This downloads the published, signed bundles for the active environment into airstrings/bundles/ at the workspace root (plus a manifest.json provenance record), verifying every Ed25519 signature before writing. Commit the folder:

git add airstrings/bundles
git commit -m "chore: update bundled fallback strings"

SDKs detect the folder automatically and seed from it on startup, re-verifying every bundle before use. Run the pull in CI or as a pre-release step to keep the committed snapshot fresh.

Shortened. The full README is on GitHub.