Translations MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRANSLATION_FILE_PATH | No | Path to the translation file (e.g., src/assets/locales/en/translation.json) |
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 |
|---|---|
| find_translationB | Find translation keys and values in the discovered translation file |
| refresh_translationsA | Manually refresh and re-index translation files to pick up any changes |
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 2 tools
The two tools, find_translation and refresh_translations, serve distinct purposes with no overlap. One is for querying translations, the other for maintenance.
Both tools follow a consistent verb_noun pattern (find_translation, refresh_translations), making them predictable and easy to understand.
With only 2 tools, the server feels under-scoped for a typical translation management system. While acceptable for a minimal server, it lacks breadth.
The server provides only find and refresh capabilities, missing essential operations like add, update, or delete translations. This leaves significant gaps for common use cases.