Shipi18n
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | Optional. Alternative provider key for the translate tools; not needed for any validator. | |
| ANTHROPIC_API_KEY | No | Optional. Used only by the translate tools; all validator tools run with no API key. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_localesA | Validate translated locale files against the source language: missing/orphaned keys, dropped or invented placeholders, collapsed plurals, empty values, untranslated copy. Deterministic — no API key and no model call required. |
| check_glossaryA | Enforce do-not-translate terms and locked per-language translations across a locale tree. Deterministic string matching — no API key and no model call required. |
| diff_localesA | Answer "what needs translating?": per language, the keys missing from the translation and the keys present that no longer exist in the source. No API key required. |
| review_localesA | Return source/translation pairs plus review criteria so YOU can judge translation quality with your own reasoning. The server performs no model call and needs no API key. Structurally broken keys are excluded — run check_locales for those. |
| list_languagesA | List the language codes and names Shipi18n recognizes (any BCP-47 code works; these have friendly names). |
| check_placeholdersA | Verify a translated string preserves all placeholders from the source (no LLM call). |
| translate_jsonA | Translate an i18n locale JSON object to one or more target languages, preserving structure and placeholders. Requires your own LLM key (ANTHROPIC_API_KEY/OPENAI_API_KEY). For key-free work use the validation tools. Legacy: the MCP client's model via sampling. |
| translate_fileA | Read a JSON locale file from disk, translate it into one or more languages, and write .json files. Set incremental=true to reuse existing output files and only translate new/missing keys. |
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 8 tools
Tools are mostly distinct, but translate_json and translate_file overlap in purpose, and check_locales/diff_locales/review_locales cover related validation concerns that could occasionally be confused.
All tools follow a clear verb_noun pattern (check_, diff_, review_, translate_, list_), with consistent and descriptive naming throughout.
Eight tools is a reasonable, focused set for an i18n workflow, covering validation, diffing, translation, glossary, and language listing without feeling bloated.
The toolset covers the core i18n lifecycle: listing languages, translating JSON/files, validating structure, checking glossaries, identifying missing keys, and reviewing translation quality. No major gaps are apparent.