AirStrings

io.github.symbionix-slPublished by GitHub account symbionix-slv0.22.3Updated Oct 24, 2026

Manage AirStrings localization strings and publish signed bundles from your workspace.

Overview

AI-generated overview

Local MCP server for AirStrings that lets an AI assistant manage localization strings, push and publish signed bundles, and run A/B experiments on strings.

What you can do
Bind a folder to an AirStrings project and check project, environment and key status, including login and environment listing with protection state and stored-key state. Add, update, remove and list localization strings in the local workspace CSVs, optionally pushing changes to the API. Push local strings to the API or pull draft strings back into the local CSVs. Sign and publish bundles to the CDN for all or selected locales. Preview a promotion diff between environments and get SDK IDs, Ed25519 public keys and snippets. Create, inspect, start, stop and promote A/B experiments on individual string keys.
When to use it
Useful when an assistant should edit localization strings for iOS, Android, web, React Native or Go apps in the same workspace the airstrings CLI uses, and push, publish to staging or manage string experiments without leaving the chat.
Requirements
Runs as a local stdio process, installed with the airstrings CLI (npm global package or Homebrew) and started as airstrings-mcp. It works on the .airstrings workspace found from its working directory. Authentication uses AIRSTRINGS_ORG_API_KEY, AIRSTRINGS_API_KEY or a stored login; with none, login returns a pending status and a verification link that an organization owner must approve in the browser.
Before you install
Writes and publishing go to staging only; production is protected and must be promoted by a human in the dashboard, and the server can only preview a promotion. Pulling overwrites local CSVs, and removing strings with push mirrors the deletion to the API. Login binds a folder to a project and needs owner approval. API key management is CLI-only.

Installation

In SourceWeft

  1. Open AirStrings in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

airstrings-mcp

MCP server for AirStrings: lets an AI agent manage strings, publish signed bundles and run A/B experiments on strings for iOS, Android, web, React Native and Go apps. JSON-RPC 2.0 over stdio, listed in the MCP Registry as io.github.symbionix-sl/airstrings-cli.

It ships with the airstrings CLI and works on the same .airstrings/ workspace, so the agent and the terminal see the same strings.

Install

bash
npm install -g @airstrings/cli                    # or: brew install symbionix-sl/airstrings/airstringsairstrings mcp install                            # Claude Code (user scope)airstrings mcp install --claude-desktop           # Claude Desktop

Any other client: run airstrings-mcp over stdio.

json
{ "mcpServers": { "airstrings": { "command": "airstrings-mcp" } } }

The server works on the workspace found from its working directory, walking up like .git.

Auth

airstrings_init binds a folder to a project. With no key it uses AIRSTRINGS_ORG_API_KEY, AIRSTRINGS_API_KEY or the stored login; with none it returns status: "pending" and a verification_uri_complete. An organization owner approves it in the browser, then the agent calls the tool again.

Production is protected: writes and publishing go to staging, and a human promotes to production in the dashboard. The server can preview a promotion but never applies one.

Tools

ToolDoes
airstrings_loginLog in and store an org key (pending until an owner approves)
airstrings_initBind a folder to a project: api_key, name, project, org, dir
airstrings_statusProject, active environment, key scope, protection and the next step
airstrings_env_listEnvironments with protection and stored-key state
airstrings_strings_setAdd or update a key in the local CSVs: key, values, format (text/icu), section, push
airstrings_strings_rmRemove a key, or one locale, from the local CSVs; push mirrors it to the API
airstrings_strings_lsList local strings, optionally one section
airstrings_pushPush local strings to the API (all or one section)
airstrings_pullPull draft strings into the local CSVs (overwrites them)
airstrings_publishSign and publish bundles to the CDN (all or some locales)
airstrings_promote_previewRead-only diff between environments + the dashboard link to apply it
airstrings_sdk_configIDs, Ed25519 public keys and SDK snippets for an environment (all public)
airstrings_variant_setCreate or replace a string's A/B experiment: allocation, variants
airstrings_variant_statusCurrent experiment for a key
airstrings_variant_start / _stopStart or stop serving the variants
airstrings_variant_promoteMake a variant the base string

API keys (list, rotate, revoke) are deliberately CLI-only.

Typical flow

  1. airstrings_init, then airstrings_strings_set once per key with every locale in values.
  2. airstrings_push, then airstrings_publish to staging.
  3. airstrings_promote_preview and hand the user the link to promote to production.
  4. airstrings_sdk_config to wire the app's SDK.

Build

bash
go build -o airstrings-mcp ./cmd/airstrings-mcp

License

MIT, see LICENSE.

Source: cmd/airstrings-mcp/README.md at commit b839a7f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

9
  1. v0.22.3LatestOct 15, 2026
  2. v0.22.2Oct 13, 2026
  3. v0.20.0Oct 8, 2026
  4. v0.18.4Oct 6, 2026
  5. v0.18.1Oct 6, 2026
  6. v0.17.1Oct 6, 2026
  7. v0.17.0Oct 5, 2026
  8. v0.15.0Sep 17, 2026
  9. v0.11.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts