Android i18n MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRANSLATION_MODEL | No | Model name for translation (optional, default depends on provider) | |
| TRANSLATION_API_KEY | Yes | API key for the translation provider | |
| ANDROID_PROJECT_ROOT | Yes | Path to the Android project root directory | |
| TRANSLATION_PROVIDER | Yes | Translation provider (e.g., openai, deepseek) | |
| TRANSLATION_LANGUAGES | No | Comma-separated list of target languages (optional, defaults to all 28 supported languages) | |
| TRANSLATION_API_BASE_URL | No | Base URL for the translation API (optional, default depends on provider) | |
| TRANSLATOR_SOURCE_LANGUAGE | No | Source language of default strings.xml (optional, default 'en') |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| translate_all_modulesA | Detect changes in all default strings.xml files using git diff and translate them to all supported languages |
| translate_moduleA | Detect changes in a specific module's default strings.xml using git diff and translate to all languages |
| check_changesA | Check for uncommitted changes in default strings.xml files without translating |
| check_missing_languagesA | Check which language directories are missing compared to configured TRANSLATION_LANGUAGES |
| create_and_translate_missing_languagesA | Create missing language directories and translate default strings.xml into them |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Tools are mostly distinct: translate_all_modules and translate_module differ by scope (all vs specific module), while check_changes and check_missing_languages have clearly separate purposes. The create_and_translate_missing_languages tool also stands apart by focusing on directory creation plus translation. Only minor overlap exists between the two translate tools.
All tool names follow a consistent verb_noun pattern in snake_case: translate_all_modules, translate_module, check_changes, check_missing_languages, create_and_translate_missing_languages. The pattern is predictable and uniform.
5 tools is well-scoped for an i18n server. The set covers translation, change detection, and language directory management without excessive overlap or missing essential actions.
The toolset covers the core workflows: detecting changes, translating, checking missing languages, and creating missing language directories. A minor gap is the lack of a tool to explicitly list configured languages or operate on a single language-specific translation, but these are not critical for the main purpose.