
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
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.
Installation
In SourceWeft
- Open AirStrings in the dashboard and add it to a workspace.
- 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
Any other client: run airstrings-mcp over stdio.
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
API keys (list, rotate, revoke) are deliberately CLI-only.
Typical flow
airstrings_init, thenairstrings_strings_setonce per key with every locale invalues.airstrings_push, thenairstrings_publishto staging.airstrings_promote_previewand hand the user the link to promote to production.airstrings_sdk_configto wire the app's SDK.
Build
License
MIT, see LICENSE.
Source: cmd/airstrings-mcp/README.md at commit b839a7f
Tools
0Version history
9- v0.22.3LatestOct 15, 2026
- v0.22.2Oct 13, 2026
- v0.20.0Oct 8, 2026
- v0.18.4Oct 6, 2026
- v0.18.1Oct 6, 2026
- v0.17.1Oct 6, 2026
- v0.17.0Oct 5, 2026
- v0.15.0Sep 17, 2026
- 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