Translation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUBMED_EMAIL | Yes | Your email address (required by NCBI) | |
| PUBMED_API_KEY | No | Optional API key for higher rate limits |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| translate_keyC | Translate a specific translation key to target language(s) |
| translate_namespaceC | Translate all keys within a specific namespace/file |
| find_missing_translationsC | Identify missing or outdated translations across locales |
| validate_translationsC | Validate translation quality and consistency |
| analyze_translation_contextC | Analyze translation context and provide suggestions |
| get_configurationC | Get current configuration and detect workspace settings |
| set_workspace_configC | Update workspace-specific translation settings |
| save_translationsC | Save provided translations to locale files |
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
Each tool has a distinct purpose with clear boundaries: analyze context, find missing translations, get configuration, save translations, set configuration, translate a key, translate a namespace, and validate translations. There is no overlap in functionality, making it easy for an agent to select the right tool.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'analyze_translation_context', 'find_missing_translations', and 'save_translations'. This predictability aids in understanding and usage without any deviations or mixed conventions.
With 8 tools, the server is well-scoped for translation management, covering configuration, translation operations, validation, and analysis. Each tool serves a specific role, avoiding bloat or thinness, making the count appropriate for the domain.
The tool set provides comprehensive coverage for translation workflows: configuration management (get/set), translation operations (key/namespace), saving, validation, and analysis for missing translations and context. There are no obvious gaps, supporting full CRUD-like lifecycle handling.