What AirStrings MCP server does
The AirStrings MCP server exposes workspace and localization operations for the AirStrings service. It can initialize a project workspace, add or update translated strings, remove strings, list local entries, synchronize draft strings with the remote API, and publish locale bundles to the CDN.
AirStrings supports over-the-air string updates for iOS, Android, web, React Native, and Go applications. The MCP workflow is intended for projects where an AI agent needs to edit translation data while keeping the workspace as the primary editing surface. Local CSV files can be inspected and changed without credentials, then synchronized when the workspace is ready.
Publishing is separate from draft synchronization. The publish operation sends bundles to AirStrings, which signs them with Ed25519 before placing them on the CDN. Client SDKs verify the signature before using the bundle.
How it works
After workspace initialization, the project directory contains AirStrings configuration and local CSV data. The active environment is staging by default. airstrings_strings_set and airstrings_strings_rm change local data; each also supports an optional push operation that immediately mirrors the change to the API. airstrings_push synchronizes local strings in bulk, and airstrings_pull retrieves remote draft strings into the workspace.
airstrings_strings_ls reads local strings for offline inspection. This is different from pulling published bundles: draft synchronization produces editable CSVs, while published bundles are immutable delivery artifacts. The CLI can also download signed published bundles into a workspace directory for offline application startup, but that operation is separate from the listed MCP string and publishing tools.
Production environments are protected by default. Direct writes and publishing are rejected there; changes must be promoted from staging by a human or by an authorized full-power organization key. This makes the AirStrings MCP server better suited to controlled staging workflows than unrestricted production mutation.
Setup and configuration
Install the AirStrings CLI through npm, Homebrew, or Go, then register the MCP server with Claude Code using airstrings mcp install. The npm package requires Node 18 or newer. Source builds are also supported from the repository.
Run initialization from the project directory. Without a key, initialization opens a browser login flow, stores an organization key in ~/.config/airstrings/credentials.json, creates or selects a project, and writes .airstrings/config.json. A project key can instead be supplied directly to bind the workspace to an existing project.
Credentials may come from AIRSTRINGS_ORG_API_KEY, AIRSTRINGS_API_KEY, the workspace configuration, or a stored login, in that precedence order. Project keys cover all environments for one project. Organization keys can cover multiple projects, while legacy environment keys apply to one environment and are deprecated.
Tools and capabilities
The AirStrings MCP server provides these tools:
airstrings_init: Initialize the workspace and bind it to an AirStrings project.airstrings_strings_set: Add or update a key in local CSV files, with optional immediate API synchronization.airstrings_strings_rm: Remove a key or locale locally, with optional remote deletion.airstrings_strings_ls: List strings stored in the local workspace.airstrings_push: Send local strings to the AirStrings API.airstrings_pull: Retrieve remote draft strings into local files.airstrings_publish: Publish bundles for delivery through the AirStrings CDN.
Use the server when translation edits should be reviewable in the workspace before synchronization, when an agent must keep local and remote drafts aligned, or when publishing signed locale bundles is part of a release process.