Xcstrings MCP Server
Manage Apple String Catalog files with precision localization and batch processing.
Data last scanned today · Reviewed today
Overview
Xcstrings MCP Server provides a specialized interface for handling .xcstrings files, the modern localization format for iOS and macOS. By acting as a middleware between your AI assistant and your local files, it allows for granular operations like batch key translation, CLDR plural validation, and XLIFF import/export without exhausting your context window. The server is built in Rust to maintain high performance and ensure that file writes remain byte-identical to Xcode's output. It handles common localization challenges including legacy .strings migration, format specifier checking, and glossary maintenance to keep terminology consistent across your application's project files.
Our verdict
This server carries a high risk level with a security score of 33/100, primarily due to the lack of a read-only mode, which grants the tool full write access to your project files upon installation. As a community-maintained project with a single contributor, it is best suited for experienced developers working in isolated environments who need to automate complex string catalog tasks and can manually verify the integrity of atomic file operations.
- Zero direct dependencies reduce potential supply-chain vulnerability surfaces
- Maintains exact Xcode JSON formatting including key order and spacing
- Validated support for complex CLDR plural forms and format specifiers
- Provides migration paths from legacy .strings and .stringsdict files
- Full write access is granted to all managed files by default
- Not an official vendor-maintained tool, relying on a single contributor
- Security model relies on unverified community implementation
Tools
| Tool | Description | Risk |
|---|---|---|
| parse_xcstrings | Parse and cache .xcstrings file | low |
| get_untranslated | Get untranslated strings with batching | low |
| submit_translations | Validate and write translations atomically | medium |
| get_coverage | Per-locale coverage statistics | low |
| get_stale | Find stale/removed keys | low |
| validate_translations | File-wide validation report | low |
| list_locales | List locales with stats | low |
| add_locale | Add new locale with empty translations | medium |
| remove_locale | Remove a locale from all entries | medium |
| get_plurals | Extract keys needing plural translation | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›Does this server alter the formatting of my .xcstrings files?
No, the server performs atomic writes that strictly match Xcode's JSON formatting, including specific colon spacing and key ordering.
›Can I migrate my existing .strings and .stringsdict files?
Yes, the server supports legacy migration from both .strings and .stringsdict files, including handling of plural rules and positional specifiers.
›How does the server handle large files that exceed the AI's context window?
The server allows you to pull and translate keys in smaller, manageable batches of 50 to 100 entries at a time.
›Does the server provide any verification for translations?
Yes, the server performs validation for CLDR plurals and format specifiers, such as ensuring %d and %@ placeholders are correct before saving.
›Is it possible to export translations for use in external tools?
Yes, the server supports importing and exporting XLIFF 1.2 files to facilitate workflows with external translation platforms.
›How are multiple .xcstrings files handled in a single project?
You parse each file individually to cache them; the server tracks which file is currently active and allows you to switch between them.
Badge
Maintain this server? Add the live badge to your README.