"Files" matching MCP servers:

AI localization from your editor — translate an app's string files into 46 languages with placeholder-safe, reproducible output. Eleven formats (JSON, .arb, .po, .strings, Android XML and more), and every translation is read back and checked before it lands.

Delegates mechanical text-to-text tasks to a local LLM to save Claude subscription quota, reading files server-side so large content never enters Claude's context.

Enables agents to speak Thai and English audio through local speakers, manage a playback queue, save speech to files, translate text into Thai, and OCR PDFs and images.

Enables law firms and legal professionals to turn Arabic and English contract files into structured, citable context, with clause segmentation, date conversion across Hijri and Gregorian calendars, party extraction, and anchor-based verification, all without API keys or network calls.

Enables translation of Excel files using Claude AI while preserving formatting, formulas, and data integrity.

A Docker-based MCP server wrapping the Smartling CLI, enabling natural language management of translation projects, files, and glossaries.

MCP server for HumanPen that lets AI agents work on real documents (.docx, .pptx, .pdf) — humanizing content to lower AI-detection scores, converting citations, condensing, and translating while preserving formatting, tables, images, and citations.

An MCP server for managing Rails-style localization files (YAML/JSON), enabling coding agents to read, search, write, and audit translations without hand-editing files.

An MCP server that automatically translates Android app string resources to multiple languages by detecting changes in default strings.xml files using Git diff. It supports batch translation, preserves formatting placeholders, and works with multiple Android modules.

MCP server for managing i18n translation files — gives your AI agent full control over your app's translations without dumping entire locale files into context.

A Model Context Protocol server for reading, writing, and managing GNU Gettext .po translation files, enabling language models to perform file operations, entry management, partial updates, and fuzzy entry detection.

Enables processing and translating SRT subtitle files with intelligent conversation detection and context preservation. Supports parsing, validation, chunking of large files, and translation while maintaining precise timing and HTML formatting.

Enables automatic discovery and fast searching of translation files in projects, supporting partial/exact key-value matching with file watching and multiple translation file formats.

Provides tools for working with iOS Localizable.xcstrings files, enabling automated translation workflows and localization management for iOS/macOS projects using Xcode String Catalogs.

Counts characters and words in both Japanese and English text files, with special handling for Japanese morphological analysis and proper character counting excluding spaces and line breaks.

Enables AI assistants to manage i18next translation files, including adding keys, syncing missing translations, and analyzing coverage.

A server that provides translation capabilities using TranslationX API, enabling users to translate files and content through natural language commands.

An MCP server for processing XLIFF and TMX translation files, enabling parsing, validation, and manipulation of translation units in localization workflows.

An MCP server for internationalization (i18n) tasks, providing tools to translate, move, list, and remove translation keys in JSON files for the Kilo Code extension.

Translation QA for i18n locale files. Deterministic validators — missing keys, placeholder drift, collapsed plurals, glossary breaches — that need no API key, plus a review tool that hands translation pairs and judging criteria back to the calling agent, so meaning-level review runs on the model your client already has. Translation with your own LLM key is optional. JSON, Flutter .arb, Apple .